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:latestThis 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?
BenB
-
G girish referenced this topic on
-
(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:latestThis 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?
@benborges Would be great to have this packaged.
As for the volume sharing:
-
Think of appsdata (aka 'app data' aka 'data directory') as application local data and something which has structure internal/private to an app. Sort of like an app's internal database. Other apps should not really be reading or writing to this.
-
With that in mind, ideally, you scaper LAMP app can write to say some custom location. So, this can be configured then as '/mnt/scraped-data
which is your Cloudron volume namedscaped-data` -
The fileshare app would also have this volume mounted (as readonly i guess). The end user after installing fireshare would change the /app/data/env to point to this
/mnt/scraped-data.
-
-
@benborges Would be great to have this packaged.
As for the volume sharing:
-
Think of appsdata (aka 'app data' aka 'data directory') as application local data and something which has structure internal/private to an app. Sort of like an app's internal database. Other apps should not really be reading or writing to this.
-
With that in mind, ideally, you scaper LAMP app can write to say some custom location. So, this can be configured then as '/mnt/scraped-data
which is your Cloudron volume namedscaped-data` -
The fileshare app would also have this volume mounted (as readonly i guess). The end user after installing fireshare would change the /app/data/env to point to this
/mnt/scraped-data.
- 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?
BenB
-
-
- 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?
-
@benborges Do you have an initial code/package already? Might be easier for me to understand with the code.
