Migrate clowdr-backend repository

[dorranh]

This PR addresses the first point of https://github.com/clowdr-app/clowdr-web-app/issues/269, which is to migrate the content of the clowdr-backend to this repo.

I've essentially just copied over the content of that repo with minimal renaming, etc., so the developer workflow should be nearly the same as before. I've tested the TS build locally but haven't been able to test deploying to Heroku since I don't have access to that.

Edit: The deploy process for Heroku will be different now that clowdr-backend is in a subdirectory. If you have a dev environment I'm happy to help configure the deploy scripts as well.

[EdNutting]

Hi Dorran,

Thank you for this. We're crazy busy trying to get everything ready for SPLASH on Sunday so please forgive me being a bit slow to respond.

Currently we deploy to Heroku by just pushing the git branch up to their remote. I would really appreciate it if you can look into how we can configure a script that just deploys the relevant folder? (Even better if we can formulate it in a way that enables some kind of automated-release system from the stable branch?)

Thanks!

[dorranh]

Hi @EdNutting,

I hope SPLASH went well! For Heroku it looks like you can get around their limitations for monorepos by pushing a git subtree. This is short enough that I don't think that it necessarily needs a script, though once we confirm that this works for you I can add some instructions to the docs. Basically you just:

1. Create the N different apps in heroku as normal (skip if they already exist)
2. On your dev machine, add each app's heroku git repo as a separate remote (e.g. git add remote heroku-clowdr-backend some/url.git)
3. Push the subtree. If you are pushing to an existing git branch on the heroku remote you may need to force push: git subtree push --prefix backend/clowdr-backend heroku-clowdr-backend dev

This process should be trivial to automate in a CD pipeline - for that it might be best if we touched base over email/phone.

Cheers, Dorran

[rossng]

Thanks for the help here Dorran. We've been very busy with SPLASH stuff until now, as Ed said!

We're currently experimenting with a completely new repository based on our learnings at SPLASH, so I'm going to hold off on merging this PR for now. If you still had clowdr-db-schema on your todo list, don't worry about that 🙂. And sorry if you have spent lots of time on it in the background :s

(p.s. Useful to know the git subtree trick - I didn't know about that.)

[dorranh]

Hi @rossng, thanks and no worries - I've been out on holiday the past week :slightly_smiling_face:. That sounds good! Let me know if you guys end up having any questions for us on setting up builds, etc.