add more documentation to set up

[L0ric0]

it would be nice to have the full documentation for a setup without docker. also the information if the mysql database is replaceble with prosgres (some datatypes are different)

[V13Axel]

Couple of things here that come to mind here:

1. The docker-compose.yml file in this repo is designed for development, not production. Don't run it in production that way.

2. There is a docker container published to dockerhub for every release, so if you do want to run it in Docker, you should use the Docker image tfantasycalendar/fantasycalendar alongside your database, instead of the included docker-compose.

3. A general docker-compose template for proper deployment is probably a good idea. I think I'll try and make that happen at some point.

4. Fantasy Calendar is just a Laravel app - You can find information about deploying Laravel applications here:

   https://laravel.com/docs/8.x/deployment

   The only thing made trickier about FC is that the database setup is done from a raw SQL file at the moment, and then Laravel migrations are run on top of that file.

   That's the result of pre-Laravel FC days, and should go away sometime in the future when we get proper Laravel migrations written (making it as simple as artisan migrate). However, at the moment I can't guarantee whether that approach will or will not work on postgres. Given there are calls like Engine=InnoDB in there, I doubt it would work without some modifications.

[L0ric0]

thanks for the help. I have tried deploying fantasycalendar as written in 4. but encountered problems with the url generation of lavarel.

I want to deploy fantasycalendar at domain.tld/fantasycalendar. for this i put APP_URL = https://domain.tld/fantasycalendar into the config. Whith this fantasycalendar tried to load the static recources from the rout path (domain.tld/) this could be fixed by setting ASSET_URL and MIX_ASSET_URL to the same als APP_URL this fixed the loading of the css and js recources but the custom fonts are still being loaded from the root.

Also all links on the mainpage are wrong. They are generated as domain.tld/fantasycalendar/index.php/calendars/create which should be domain.tld/fantasycalendar/calendars/create under which path the site can be found. The fixed link leads to an errorpage of lavarel with an exception saying that lavarel is unable to find the mixerfile which it trys to find in the root of the server and not in the subdirectory.

---

For postfix the sql file had to be modified but artisan was able to run the migrations (all but one as one clumen did not have a default, which was pretty easy to fix). I will add a PR when i get fantasycalendar to run and have tested it.

[tctlrd]

2. There is a docker container published to dockerhub for every release, so if you do want to run it in Docker, you should use the Docker image tfantasycalendar/fantasycalendar alongside your database, instead of the included docker-compose.

Hi @V13Axel, is it possible to see a docker image created for the latest release? Currently there is only one image from three years ago on docker hub. Thank you!

[V13Axel]

The Docker image build has been broken for a really long time because we stopped using it in our production setup - However, I did recently take interest in fixing it, and have started work on a fixed version. I'll see what I can do sometime soon @tctlrd

[tctlrd]

That would be wonderful! I will put it to great use. @V13Axel

[Nebula-0-System]

any updates on this? i found this project a few months back, and had the intention of getting it running myself on my own server and taking it for a spin, but documentation to running a ready-to-use version is entirely lacking, and the dockerhub container is still outdated. the project seems like it's awesome, but the ability to get it working on one's own is really lacking it seems. docker-compose is still used in make and throwing errors for one, and that's for a development version, and the prod/ready to use version on docker hub is out of date.

should i try finding a different program/tool or is this gonna be fixed anytime soon @V13Axel?

(all /neu and /genq btw. it looks awesome, i just, wanna save money and run it myself lol)