I’m also waiting for this to move some 500 repositories from GitHub to a realistic federated alternative. I follow up from a distance but don’t see much movement on ForgeFed for ForgeJo. Did I miss something?
I’m also waiting for this to move some 500 repositories from GitHub to a realistic federated alternative. I follow up from a distance but don’t see much movement on ForgeFed for ForgeJo. Did I miss something?
I don’t think Xerox invented the computer mouse. It was first drawn out by Douglass Engelbart and presented to the public in the 1968 presentation “Augmenting the Human Intellect” (you can watch it on the present day, it was recorded).
It was my understanding (which I did not verify) that this was picked up by Xerox and others and that windowing systems evolved from there on with Xerox leading towards Desktop Publishing.
This must be from another timeline. Sorry for the inconvenience, please skip.
User focused applications running on my own internet accessible infrastructure fully based on open standards and interoperable with the Fediverse… Yes please
I’m looking forward to play with this.
You could find out about the way we do it at https://github.com/madnificent/docker-ember but I would not if I were you.
The real risk, today at least, does not seem utterly huge. Jumping in this rabbit hole of containers is another topic in itself. I suggest continuing your learning as you do now and maybe revisit this later. You will learn faster that way.
Feel free to check what we did on the link above and ask questions later or whenever you feel ready for this topic.
You shouldn’t eat candy given to you by strangers. If you’re in a large group and someone knows the candy, maybe. Code is food for your computer. Be wary. Our large Open Source group of friends has learned about many kinds of candy and shouts loudly when some in the group becomes ill. You don’t want to become ill. Some risk exists, but with a large group it is generally ok. Don’t install packages as root, don’t install what you don’t need.
I run my frontend builds through Docker (also during development). By isolating access to the host system to the files/folders necessary for development I’ve shielded off the majority of current realistic attacks I’ve seen as NPM based exploits. I’m certain the approach can be replicated for other frameworks, but we use Ember and docker-ember. I doubt it runs as smoothly on a non-Linux OS.
Looks good to me.
docker-ember largely automates such a setup with specific mounts for linking node modules from other folders, being able to bind to localhost for when you run the backend on your own machine, and exposing ports for livereload. May include other secret sauce. Some of that is closely tied to EmberJS.
I’m a fan of using tools you understand. What you show here is comprehensible and sufficient for now👌