@girish Haven't' pushed anything cloudron related yet but my repo is here https://git.osintukraine.com/benb/fireshare
Posts made by benborges
-
RE: Help packaging fireshare
-
RE: Help packaging fireshare
- Other apps should not really be reading or writing to this.
Fireshare would never write to the other container, it would just read it and index the file to its own sql database inside its own data container, the video would reside on the LAMP container and would only be read by Fireshare and publicly served.
- what's the difference to say, a custom mount point and say /home/yellowtent/appsdata/cc81fa5c-a060-4fb8-bcaa-c13b009b0c43/data/public/media (which is the actual data volume of an existing LAMP ?
isn't it just a convention ?
so if 2 can be done, either way, custom mount of direct path to existing data volume, can I conclude that i should package fireshare as if the /mnt/scraped-data was the data volume used by the package addon and then, once the app is running, edit the .env file and point it to an arbitrary path/custom mount?
-
Help packaging fireshare
(warning, war content) My test use case : http://osintukraine.com:9090/#/feed (use incognito to accept the self-signed cert)
I have a question for @girish maybe, I'm going to package Fireshare code for cloudron
but I'm wondering if by using the .env provided I will be able to point the //path/to/my_game_clips: folder (source)
to another cloudron LAMP container (running the scrapping of videos) such as /home/yellowtent/appsdata/cc81fa5c-a060-4fb8-bcaa-c13b009b0c43/data/public/mediadocker run --name fireshare -v $(pwd)/fireshare:/data:rw -v $(pwd)/fireshare_processed:/processed:rw -v /home/yellowtent/appsdata/cc81fa5c-a060-4fb8-bcaa-c13b009b0c43/data/public/media:/videos:rw -p 8080:80 -e ADMIN_PASSWORD=your-admin-password -d shaneisrael/fireshare:latest
This is the test link above, I'm currently running and it works fine outside of a cloudron package so i'm wondering, can I have variable pointing to another data volumes on a different app/container?