this is a dumb nodejs server and front end that I made to help with calorie and macronutrient tracking. It's real simple and made for me to use by myself so there aren't a lot of fancy UI features. Mostly it lets me do what I want to do and it's coded in a way to help me test out some ideas I had.
so far I've been running it for over a year with no major crashes or bugs, but that's not that impressive when we are talking about 1 user that's also it's creator.
there are basically 3 important directories of code lib, which contains files the server needs, src which is for the front end and sql which is for the database.
the server uses teejay to be set up, meaning a lot of the code is kinda generic stuff that you fill in details in the configuration. There are 2 configuration files, the environment, which sets up globals (right now the only gloabl is the database connection.) and the server configuration which sets up the routes.
the front end is based around a bit of code I made to kinda-sorta work like elm, but just in JS. I didn't wanna mess with too many dependencies to do like react or vue or whatever the JS framework of the month is, and I didn't wanna do elm because well, no real great reason I just didn't like the way it looked. It's based around virtual dom and only really depends on that. However due to modern front ends being what they are that means I also used parcel to build it all. I'm not much of a "front end guy" and I try to avoid doing much stuff with all the various build processes and transpilers and whatnot.
the database folder just has a nice file called "setup.sql" that you can pipe directly into a postgres database and it will set things up the way this app likes. I haven't bothered figuring out a way to do non-postgres or anything more generic, but you should be able to look at that file and figure out what you want if you want to use a different DB, it's only 3 tables and a view.
the idea behind teejay was to be able to have the config hosted by something like zookeeper or in a database to allow for easy customization / updating of services in flight. I haven't built that system yet so this program just loads the tj files off the hard drive. I don't commit these configuration files because they have things like passwords in them, however they are absolutely critical and actually define a lot of the features.
therefore you can take a look at examples in the wiki to see how they work. The server.tj file there is almost the same as the actual config file I use in production.
the sever doesn't require any build processes, just install the dependencies (I use yarn for that but I think npm will work too I haven't tried.) Just start it up with '''node main.js ''' those paths will default to './conf/test.tj' and './conf/server.tj' respectively.
the front end no longer requires a build step, it's just raw html and javascript classic "open web" style, the whole system is small so there isn't much need for minifying or doing anything fancy yet.