Skip to content
This repository has been archived by the owner on Feb 16, 2024. It is now read-only.

Attempting to modernize & deploy the app #39

Open
unquietwiki opened this issue Mar 1, 2018 · 5 comments
Open

Attempting to modernize & deploy the app #39

unquietwiki opened this issue Mar 1, 2018 · 5 comments

Comments

@unquietwiki
Copy link

Hey @Aldaviva & all. Where I'm currently working (a VFX shop), the boss was looking for a good floor plan solution. We came across this, and it seemed to be really promising. However, it looks like the code base is a few years old: deploying it on an updated Node+Mongo combination, doesn't seem to be that straight-forward. I'm not a Node.js guy, but I am a "jack of all trades", so figured it would be interesting to see what would happen in trying to get this app modernized (also grateful to said boss for letting me try). Think it's mostly there: followed most of the porting advice I could find for going to Express 4; applied StandardJS formatting; tried to update the MongoDB handler; implemented logging & custom directories.... It's still not fully there though. Can you all take a look please?

https://github.com/unquietwiki/floorplan

@unquietwiki
Copy link
Author

I forgot to add this earlier: one thing I think might be necessary / relevant, is the proper handling of running the app behind a reverse proxy (IIS, Caddy, etc). There was some vague logic, that seemed to indicate stripping out the external path on the server-side, but apparently keeping it on the client-side. I found a module that might better apply, but hadn't had a chance to try it out (wasn't even sure if it's a necessary step).

https://github.com/chimurai/http-proxy-middleware

@unquietwiki
Copy link
Author

Wanted to update everyone.

  • I decided I didn't need the proxy-middleware. connect-slashes appears to work for whatever was going on before; far as I can tell.
  • I've gutted & re-done the main routing & database logic.
  • I've expanded the configuration with additional options.
  • De-globalized the "app" and "router" classes (had globalized them as an attempt to get things going); left the configuration globalized for sanity.

App itself doesn't seem to "work" still, but the back-end is showing signs of life.

@unquietwiki
Copy link
Author

Switching over to FeathersJS seems to have worked. Still trying to figure out how to get the SVG data to show up in the browser: it's showing up in the HTML source at least.

https://github.com/unquietwiki/floorplan

@unquietwiki
Copy link
Author

Confident the backend code is mostly "done"; the front-end relies on some library code that was behind. The main front-end JS is now more like ES2015; however, the libraries being used have mixed support for the "import" clause. Going to need to figure out how to get them to work with System.js; Require.js & another thing I looked at seem to not work as well for this mix of things.

@unquietwiki
Copy link
Author

Hey @Aldaviva . I got laid off 3 weeks ago, and been doing a mix of things at home; alongside trying to find a new job. At last check, I had some Backbone.JS devs (constructively) arguing over how to proceed with getting that to work right with an ES2015+ application. I wouldn't mind trying to get this effort finished, per what we discussed in email a few weeks ago. I'm going to make a pull request; that I'd like put into a 3.0 branch (did something similar with the PassCore guys, and trying to get something like that going for NAPS2). This way, the work that has already been done, doesn't get totally lost; and maybe we can get some additional help on this. Thanks.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant