Hacker News new | ask | show | jobs
by thorncorona 1291 days ago
The only reliable solution to this that I have found is compiling an app into a docker container and ensuring my projects are able to run off a SQLite database.

I then save this to my NAS.

Otherwise literally everything will break.

Running an app that I wrote only 3 years ago will blow up.

1 comments

I don't understand: if you have fixed dependencies and the same Nodejs version, how can things break?

I'm not saying it's a good thing to not update your packages but you seem to imply there's another force messing with your project?

In general it's a hassle when your processor arch, OS version, and node version starts to come into play. NPM doesn't handle this in a great way, especially with native dependencies that need to build, and rely on OS apis. NodeJS isn't particularly stable either.

For example, I used to dev apps on windows, and run them on Ubuntu 16. That worked alright but required minor changes. Moving to Ubuntu 20 on my server required a couple tweaks, and then later moving to deving on Mac required more changes.

Of course keeping old copied of databases is a different story but SQLite is just so convenient compared to backing up full fledged SQL dbs.

These were for old finished projects I wanted to briefly spin up.