An unofficial CLI for Neocities. It uploads folders quicker than the official CLI by batching them, and comes with the ability to download your website.
Note: I'm new when it comes to FOSS and CLI
Neomanager is way faster than the official one. In some cases, it finishes by the time the official CLI even starts uploading anything. See for yourself in the video.
comparison.mp4
| Neomanager | Official CLI | |
|---|---|---|
| Uploading | ✅ | ✅ |
| Stress test (video above) | 21s | 2m 5s |
| Downloading | ✅ | ❌ |
| Progress bar | ✅ | ❌ |
| Install method | npm | RubyGems |
| File list | ❌ | ✅ |
| Deleting | ❌ | ➖¹ |
| .gitignore support | ➖² | ✅ |
| Site info | ✅ | ✅ |
| Pizza | ✅ | ✅ |
¹: Manual
²: Uses .neomanager-ignore. Lacks an option to disable or set using flags, but includes a catch-all for supporter-only files.
Make sure you have Node installed, and then run:
$ npm install --global neomanager
$ neomanager upload .
224 uploading (4364 skipped)
▐█████████████████████████▌ 100%
507.15KB/507.15KB
Done.
If Neomanager detects that the exact file is already uploaded to your website, it'll skip it.
It also supports an ignore file called .neomanager-ignore. It uses the same syntax as .gitignore, but with some differences:
- Adding
#*supporterwill ignore all supporter-only file types. - You have to specifically ignore
.neomanager-ignore.
Neocities will error out and fail to upload if you upload too many files at a time. So, Neomanager gets around this by uploading files 20 at a time. The downside to this is that Neomanager has to wait on Neocities has to process the upload, which is what's going on during the (finishing up) phase.