Socioboard-5.0
Socioboard-5.0 copied to clipboard
socioboard
docker support
The first step to making a docker compose script would be to make a bash script to install. No one has published one yet.
I will take a look at what's required to get this running in docker and script the install process. This seems like an interesting and useful platform and if it can help us with our social media workload I would be happy to work with you to contribute this
I will take a look at what's required to get this running in docker and script the install process. This seems like an interesting and useful platform and if it can help us with our social media workload I would be happy to work with you to contribute this
I'm happy to set it up with you.
@mtcaddy sorry, I commented after just discovering the software and not trying it out. I signed up to the free plan of the commercial version and it had so many bugs that it was unusable. Lots of CORS issues in the front end. I would like this software to be worth my time, but right now it isn't.
@rsmithlal Can you share your scripts? Making issues for the CORS issues would help too.
@TechnologyClassroom I didn't end up writing more than just the initial couple of empty files because realized that I hadn't tried the software yet and had no idea what it was like or if it was worth investing time in. The bugs that I encountered were with the commercial production software and not the open source edition, and they don't have a clear way of reporting issues with that software as far as I could see. No contact email listed or open bug tracker portal.
@rsmithlal I see. I think this is also the bug tracker for that.
@rsmithlal Did you find an alternative since Socioboard appears to have bugs and not worth dockerizing right now?
Unfortunately not! I didn't need the features bad enough to keep looking extensively. It's something that I will be building into my open source community engine, though. It's not released yet, but you can find it in my profile if you're interested in something like this and would like to keep up to date and/or help build it! ---- On Tue, 24 Nov 2020 20:29:38 -0330 [email protected] wrote ---- @rsmithlal Did you find an alternative since Socioboard appears to have bugs and not worth dockerizing right now?
—You are receiving this because you were mentioned.Reply to this email directly, view it on GitHub, or unsubscribe.
sadly not going to happens since it has been "requested" for about 3 years already
How about you people create your own container setup and publish it?
Open Source is about collaboration :)
How about you people create your own container setup and publish it?
Open Source is about collaboration :)
Very true, but my guess is people who could create their own container setup wouldn't be asking for one here :-)
but my guess is people who could create their own container setup wouldn't be asking for one here
Very true. If I had the knowledge or the time to learn it, I wouldn't be asking here :p
Anyone still looking at this? I'm currently working on a Docker solution. However the lack of comprehensive documentation is making it quite difficult. Is there anyone I can discuss this with? I just need a breakdown on the configs(are they loaded individually? Does "NODE_ENV=development" decide whether "development.json" is loaded instead of "default.json"?). I have yet to use the software, but I would like to and don't mind contributing if it doesn't take up too much time. I'd have to dive into the code to find such things.
@vaughngx4 The closest thing to GNU/Linux documentation is the work that was posted to issue 112. What I wrote earlier in this thread still applies. Once we have a functional bash script to install and configure a working site with sane defaults, a docker file would be trivial to make. On the other hand if someone were to make a docker compose file out of the findings from that issue, making a bash script from the docker file would also be trivial.
@TechnologyClassroom Thanks! I am separating to avoid running all services in a single container, I won't separate the api from the frontend to avoid any unexpected errors. So far I have 3 containers being socioboard, socioboard-mysql and socioboard-mongo. Using alpine as the base image for the main container. Question: Is it necessary to set social media api details and/or mail details in the configs or can that be done via the frontend?
Sounds reasonable. Carry on.
I think that is all handled in the configs, but I have not actually seen the web interface yet other than screenshots others have posted.
I faffed around with containerizing it on stream the other day if anyone is interested. Keep in mind I hadn't found all the docs and stuff at that point xD - https://www.twitch.tv/videos/1517387240
@TechnologyClassroom Thanks! I am separating to avoid running all services in a single container, I won't separate the api from the frontend to avoid any unexpected errors. So far I have 3 containers being
socioboard,socioboard-mysqlandsocioboard-mongo. Using alpine as the base image for the main container. Question: Is it necessary to set social media api details and/or mail details in the configs or can that be done via the frontend?
The developers have mentioned in one of the setup videos that it has to be done in the configs in the backend. Not sure why as it does have a frontend for it.
@jon4short I see, thank you. In the video above I was using sed but I've switched to editing with jq since the placeholders in the config files are not uniform. I've added Docker env vars for each entry in the config that needs to be changed. All local.socioboard.com and localhost entries will be replaced with the domain specified in Docker env. So there will be options to set all configs from the backend(copy pasted for like an hour but it works). Will open a PR when it's done.
@vaughngx4 The closest thing to GNU/Linux documentation is the work that was posted to issue 112. What I wrote earlier in this thread still applies. Once we have a functional bash script to install and configure a working site with sane defaults, a docker file would be trivial to make. On the other hand if someone were to make a docker compose file out of the findings from that issue, making a bash script from the docker file would also be trivial.
@TechnologyClassroom Are these 3 lines of config still necessary?
"base_path": "../../media",
"payment_path": "../../media/payments",
"template": "public/template/paymentTemplate.html"
@TechnologyClassroom Are these 3 lines of config still necessary?
¯\(ツ)/¯