Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Review OVPSync and make sure it's working well #2

Open
16 of 22 tasks
donut opened this issue Oct 22, 2021 · 4 comments
Open
16 of 22 tasks

Review OVPSync and make sure it's working well #2

donut opened this issue Oct 22, 2021 · 4 comments

Comments

@donut
Copy link
Owner

donut commented Oct 22, 2021 •
edited
Loading

  • consider saving/committing changes to separate branch
  • revert changes
  • start new branch
  • look for workable opam and/or dune dockerfile: https://hub.docker.com/r/ocaml/opam
  • setup local, basic Dockerfile
  • run new dockerfile
  • ssh into new container
  • setup opam
  • setup dune
  • add packages from package.json (alternatively, try compiling and add packages as they're found missing)
  • update app Makefile to work with opam & dune
  • get application to running state
  • add stages to dockerfile for dev and production
  • test out
  • clear out remaining esy trappings
  • get running on production
  • look through prod log for problems
  • address found problems
  • look into upgrading OCaml and OPAM packages
  • for videos that require a passthrough, tag them with "Passthrough by OVPSync" (check that follows the convention we've been using)
@donut
Copy link
Owner Author

donut commented Nov 2, 2021 •
edited
Loading

This might be a good admin solution:
https://www.getmotoradmin.com
http://hn.premii.com/#/comments/29080790

@donut
Copy link
Owner Author

donut commented Feb 3, 2022 •
edited
Loading

I'm having trouble getting the project to compile. While I'm not sure that the root of the issue is the esy build system, I plan to move to straight opam & dune instead. Hoping that going through that transition will help weed out the issues I'm having.

For the long term, I think this is a good move. As much as I appreciate the convenience of esy when it's working, I'm sure that a more typical setup with opam and dune will have more resources online for troubleshooting.

@donut
Copy link
Owner Author

donut commented Feb 8, 2022

The migration of opam/dune from esy is basically done. Only thing left to do is test it on production and fill out the stages in the Dockerfile. Definitely a good move. esy was too much of a black box.

donut added a commit that referenced this issue Feb 11, 2022
@donut
build: move to pure opam/dune build process
242b02d 
issue #2
donut added a commit that referenced this issue Feb 11, 2022
@donut
build: fix errors when running tasks from host
2e4810c 
When calling a Makefile task using docker-compose, the OPAM env would
not be setup properly. This fixes that, if kinda clumsily. Tried a
few different things to get `eval $(opam env)` to run before any task
instead at every OPAM-dependent command, but couldn't figure anything
else out. Hopefully I'll discover a better way sooner than later.

issue #2
donut added a commit that referenced this issue Feb 11, 2022
@donut
build: add required non-OPAM libs to Dockerfile
6f0de7c 
issue #2
donut added a commit that referenced this issue Feb 11, 2022
@donut
build: add undeclared mariadb dependencies
2f25b0a 
issue #2
donut added a commit that referenced this issue Feb 14, 2022
@donut
build: add build & production stages to Dockerfile
f4554e9 
Also re-organized project so everything app related (as apposed to DB)
is in the same folder.

issue #2
donut added a commit that referenced this issue Feb 14, 2022
@donut
build: remove esy trappings
a6ad05c 
We're moved over to opam/dune so all the esy stuff is no longer
necessary.

issue #2
donut added a commit that referenced this issue Feb 14, 2022
@donut
Merge branch '#2-move-off-esy'
582cca2
@donut
Copy link
Owner Author

donut commented Feb 16, 2022

So... the production server has run out of space. The solution will be to use multiple external storage devices. To accommodate this setup, OVPSync will need to be modified to handle multiple data destinations.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@donut