- 4
- 5 368
Dan on Open Source Software
United Kingdom
Приєднався 3 вер 2022
I talk about my experiences creating, maintaining and using Open Source software.
Exploring Caddy, An Open Source Web Server
I test out Caddy, an open source web server, by attempting to use it in three common scenarios that I usually use web servers for.
Intro music: "Gnadenlosz Opening" by Manuel Senfft: music.tagirijus.de
► Caddy: caddyserver.com/
► Find/Follow me: danb.me/links
0:00 Intro
0:24 Site and funding
1:40 Environment
2:26 Installation & initial config
3:52 Hosting a PHP app (BookStack)
6:44 Checking how Caddy serves
8:32 Static site on sub-path
11:32 Proxy to docker on sub-path
14:44 Closing thoughts & outro
#opensource #caddy #selfhosted #webserver #linux #ubuntu
Intro music: "Gnadenlosz Opening" by Manuel Senfft: music.tagirijus.de
► Caddy: caddyserver.com/
► Find/Follow me: danb.me/links
0:00 Intro
0:24 Site and funding
1:40 Environment
2:26 Installation & initial config
3:52 Hosting a PHP app (BookStack)
6:44 Checking how Caddy serves
8:32 Static site on sub-path
11:32 Proxy to docker on sub-path
14:44 Closing thoughts & outro
#opensource #caddy #selfhosted #webserver #linux #ubuntu
Переглядів: 2 844
Відео
Exploring Dockge, An Open Source Docker Stack Manager
Переглядів 1,9 тис.3 місяці тому
Thought it'd be fun to explore some new open source projects, and record them as a guide for others while trying to maybe add a little perspective as a fellow open source developer. In this video I explore Dockge, an open source easy-to-use docker compose stack-orientated manager. Intro/outro music: "Gnadenlosz Opening" by Manuel Senfft: music.tagirijus.de ► Dockge GitHub: github.com/louislam/d...
Companies making money from my software, is that fair? - Open Source Maintainership
Переглядів 5322 роки тому
I talk through my thoughts and experiences with others making money from my hosting my project, BookStack. Intro music: "Gnadenlosz Opening" by Manuel Senfft: music.tagirijus.de ► Follow me on Twitter: ssddanbrown ► Find me on GitHub: github.com/ssddanbrown/ 0:00 Intro 0:11 The license I use 1:24 Non open source example 4:16 View on managed services 5:27 Taking advantage via sponsor...
Handling Feature Request Bounties - Open Source Maintainership
Переглядів 1112 роки тому
In this video I share my view and experience on Open Source feature request bounties and the complex social dynamics they can introduce. Intro music: "Gnadenlosz Opening" by Manuel Senfft: music.tagirijus.de ► Follow me on Twitter: ssddanbrown ► Find me on GitHub: github.com/ssddanbrown/ #bounties #opensource #github #maintainer
awesome thanks there is 'caddy-docker-proxy' that is more suitable for docker, it's working like Traefik with tags in the docker-compose in your example with RSS, can you still access via the port ? if yes how to avoid that once you setup the reverse proxy with Caddy ? Thanks
TBH, I was never too keen on Traefik and its tag-based approach, so that's not something I'd seek. Good to have options for those that do prefer that though! Yeah, the RSS port is still accessible from the host machine (caddy will need access), but there are various ways to manage that if you're worried about external access (via local networking, firewalls and selective port forwarding).
Just click EDIT and then again on the service EDIT there you can see your storage/volume definitions.
Yeah, I had completely missed that! I thought I was already in edit mode 🤦♂
@@ssddanbrown I like this manager very much. Much more thann Portainer. Portainer is just dark voodoo hidden settings and shadow-it stuff. Nothing in it is transparent to Docker or the user. Sadly Dockge is missing an ACL User System, so i can setup users to look at logs and restart Container 1 and 3, but everything else he/she cant see. That would be wonderfull.
I see a lot of people praising Caddy but I still don't see a reason for me to switch away from nginx proxy manager
6:42 that guy looks like a real life Waluigi 😂
I hosted my site using Caddy for years. I used apache, lighttpd and nginx before. Caddy has the cleanest and easiest config I ever seen, and very much replaced nginx.
I agree it's quite impressive and has a lot of sensible defaults for modern web use cases, but it would be great if it supported Basic Auth natively without the need for third-party libraries.
Ah, does this directive (caddyserver.com/docs/caddyfile/directives/basic_auth) need a specific third-party library then?
I think it's great how you can just get started with a new tool without having to spend hours reading the documentation. Reminds me to only look up the parts I really need while I'm working on the project. And as always: a great video
Thank you Dan, nice video
More videos please! Thank you Dan
Finally I can get rid of Portainer, not that it won't fill the requirements, but it's not full docker-compose friendly, unlike what I sow in this demonstration with Dockge :).
Great look at it, and overview of what you did to bring it up and run it. BTW - a huge fan of Bookstack, so thank you for that as well!
Thanks, that means a lot coming from the master of open source app videos! Don't mean to step on your turf at all 😅
Solid points that I didn't fully consider from the maintainers point of view. The model for bounties is definitely interesting but it seems that there just needs to be more communication between the entities involved. like, maybe it really shouldn't be possible to open or pledge against a bounty without the maintainers seal of approval?
Well, I never dived deep into licensing thingies, even tho I am a big fan of FOSS stuff. In my mind Open Source was just a code that is just accessible to view by anyone, while Free and Open Source Software is the truly free code. Now I learned that they are generally the same or even exactly the same. But then how do we call a software that have license like diffgram or giving similar restrictions, while keeping the code open to view?
>> Now I learned that they are generally the same or even exactly the same. There are still some differences. All "free" code is Open Source, but not all Open Source code is "free" (As per FSF thinking). Basically, free code can ensure additional freedoms. >> But then how do we call a software that have license like diffgram or giving similar restrictions, while keeping the code open to view? "Source Available" is somewhat common. "Fair Code" is also used: faircode.io/
According to the Open Source Initiative, open source is a legal term of art. This is a legal opinion that the phrase "open source" means one and ONLY ONE thing in courts, contracts, and laws. One of the OSI's reasons for existing is to promote their Open Source Definition as the sole legal definition of open source. Does that mean you could be sued for false advertising if you advertise as open source but your software license doesn't meet that definition? Maybe, but in court systems where precedent matters, open source as a term of art hasn't really been tested
@@anthonyronda >> Does that mean you could be sued for false advertising if you advertise as open source but your software license doesn't meet that definition? I don't think so, since I don't believe the OSI has managed to gain legal ownership of "Open Source" in any way. Note the terms "legal term of art" and "legal opinion" in your message. I don't think they specifically own the term, but their efforts have pushed & popularised a specific definition. I think whether or not that would be a good thing is a whole other conversation. Could be dangerous to have a company (OSI) with that much power over the term.