atom-backend | Atom Package Registry made for Pulsar
kandi X-RAY | atom-backend Summary
kandi X-RAY | atom-backend Summary
atom-backend is a JavaScript library. atom-backend has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.
With the unfortunate sunset of Atom announcement, the community of its users couldn't allow the editor and its ecosystem to sunset with it. One major aspect of that ecosystem now lives here. The ability to search install and publish the huge repository of Packages all relied on the Backend Server that Atom had originally maintained, while the rest of the Atom project is open source and can easily be forked unfortunately the same isn't true of the Atom.io Package Repository Server. What this means is that days after the initial announcement work began to reverse engineer how the backend functioned and behaved, resulting in the original confused-Techie/atom-backend, the origins of this project. But the goals of this new Backend are twofold. Since the original creator of this repo is a part of Pulsar, the emerging fork of Atom, the eventual goal for Atom Backend has always been to serve the needs of Pulsar, its editor and its community. But in the interest of providing the most value to the Open Source community the first (v1.0.0) release of Atom Backend will be, as closely as possible, a drop in replacement of the original Atom.io Backend. Meaning that any other forks of Atom that may emerge will be able to use this repository without issue, and without any changes other than changing the URL their editor reaches out to. Even further the team that created this repo have also created the tools necessary to archive the entirety of Atom's Atom.io Package Repository. Every single package and version. This has allowed Pulsar to have a running start with a drop in replacement of a Backend Server that already contains every single package that was previously published, with of course some very few exceptions. What all of this does implicitly mean, is the repo confused-Techie/atom-backend will aim to only ever reach Feature Parity with Atom's Original Atom.io Backend Server, so that once it hits version 1.0.0 development will stop. The repo will forever aim to be an easily obtainable drop in replacement of the original Atom.io Server. But as for new features, new developments and improvements of the Backend Server will occur on Pulsar's pulsar-edit/package-backend repository, as those changes will be intended for the Pulsar Editor, and may eventually result in incompatibility with Atom. If you a user of Atom want to continue being able to install and search packages but don't want to manage your own backend infrastructure, you are able to change the URL your Atom instance points to, such as the backend in use for Pulsar. Be warned that eventually an improvement or change intended for Pulsar will break how it interacts with Atom. Unfortunately the team of Pulsar would be unable to maintain both a backend for Atom users and Pulsar users. But if someone else would like to maintain the infrastructure for Atom users, then this is the repository you need to do so.
With the unfortunate sunset of Atom announcement, the community of its users couldn't allow the editor and its ecosystem to sunset with it. One major aspect of that ecosystem now lives here. The ability to search install and publish the huge repository of Packages all relied on the Backend Server that Atom had originally maintained, while the rest of the Atom project is open source and can easily be forked unfortunately the same isn't true of the Atom.io Package Repository Server. What this means is that days after the initial announcement work began to reverse engineer how the backend functioned and behaved, resulting in the original confused-Techie/atom-backend, the origins of this project. But the goals of this new Backend are twofold. Since the original creator of this repo is a part of Pulsar, the emerging fork of Atom, the eventual goal for Atom Backend has always been to serve the needs of Pulsar, its editor and its community. But in the interest of providing the most value to the Open Source community the first (v1.0.0) release of Atom Backend will be, as closely as possible, a drop in replacement of the original Atom.io Backend. Meaning that any other forks of Atom that may emerge will be able to use this repository without issue, and without any changes other than changing the URL their editor reaches out to. Even further the team that created this repo have also created the tools necessary to archive the entirety of Atom's Atom.io Package Repository. Every single package and version. This has allowed Pulsar to have a running start with a drop in replacement of a Backend Server that already contains every single package that was previously published, with of course some very few exceptions. What all of this does implicitly mean, is the repo confused-Techie/atom-backend will aim to only ever reach Feature Parity with Atom's Original Atom.io Backend Server, so that once it hits version 1.0.0 development will stop. The repo will forever aim to be an easily obtainable drop in replacement of the original Atom.io Server. But as for new features, new developments and improvements of the Backend Server will occur on Pulsar's pulsar-edit/package-backend repository, as those changes will be intended for the Pulsar Editor, and may eventually result in incompatibility with Atom. If you a user of Atom want to continue being able to install and search packages but don't want to manage your own backend infrastructure, you are able to change the URL your Atom instance points to, such as the backend in use for Pulsar. Be warned that eventually an improvement or change intended for Pulsar will break how it interacts with Atom. Unfortunately the team of Pulsar would be unable to maintain both a backend for Atom users and Pulsar users. But if someone else would like to maintain the infrastructure for Atom users, then this is the repository you need to do so.
Support
Quality
Security
License
Reuse
Support
atom-backend has a low active ecosystem.
It has 6 star(s) with 10 fork(s). There are 3 watchers for this library.
It had no major release in the last 12 months.
There are 2 open issues and 52 have been closed. On average issues are closed in 35 days. There are no pull requests.
It has a neutral sentiment in the developer community.
The latest version of atom-backend is v1.0.0
Quality
atom-backend has no bugs reported.
Security
atom-backend has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
License
atom-backend is licensed under the MIT License. This license is Permissive.
Permissive licenses have the least restrictions, and you can use them in most projects.
Reuse
atom-backend releases are available to install and integrate.
Top functions reviewed by kandi - BETA
kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of atom-backend
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of atom-backend
atom-backend Key Features
No Key Features are available at this moment for atom-backend.
atom-backend Examples and Code Snippets
No Code Snippets are available at this moment for atom-backend.
Community Discussions
No Community Discussions are available at this moment for atom-backend.Refer to stack overflow page for discussions.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install atom-backend
You can download it from GitHub.
Support
For any new features, suggestions and bugs create an issue on GitHub.
If you have any questions check and ask questions on community page Stack Overflow .
Find more information at:
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page