a basic sunvox sharing and embedding service
  • PHP 55.7%
  • JavaScript 41.5%
  • CSS 2.8%
Find a file
Repository files (latest commit first)
Filename Latest commit message Latest commit date
2026-08-02 19:43:50 -04:00
css v0.3 - css 2026-07-28 00:19:25 -04:00
docs actual first commit 2026-04-20 12:44:29 -04:00
js actual first commit 2026-04-20 12:44:29 -04:00
test actual first commit 2026-04-20 12:44:29 -04:00
delete.php v0.3 - css 2026-07-28 00:19:25 -04:00
index.php v0.3 - css 2026-07-28 00:19:25 -04:00
play.php oops fixed url encode again 2026-08-02 19:43:50 -04:00
README.md Update README.md 2026-07-28 18:59:17 +02:00
setup.php v0.3 - css 2026-07-28 00:19:25 -04:00
upload.php v0.3 - css 2026-07-28 00:19:25 -04:00

SunBox

a basic sunvox sharing and embedding service - version 0.3 - ラミエル

this is my own instance, feel free to use it!

usage

for users

to upload a sunvox project file, select it in the form on the page. optionally, you can include your name. a unique password, used to delete your file, will be generated for you; you can copy this or set your own password.

to play files on the server, you can go to play.php. the table of files there link to the play page with the p variable set to a filename in the url. if you intend to use the player in an embed, include the e variable. if you don't want to see the detailed file information, include q.

to delete a file, you must be pn its project page and not have the e variable in the url. there will be a password form. if you put in the right password the file is deleted and you're free to upload or listen to more music.

for admins

to work properly, sunbox must be in a folder owned by the web server's user, such as apache or www-data (not the user's user like lainalien or root). to check this, move everything to where you want your service to be, navigate to settings.php, and read that. if you have that set up correctly, complete the forms on that page to create some additional directories and necessary settings files. everything should now be ready for uploads now!

for contributors

while im not gonna require that people send changes back up to me, it would be nice. uwu. if you decide to, there are some rules:

  1. no ai tooling. i'm learning on this project and offloading thinking to some computer is not condusive to that.
  2. name variables descriptively and leave good comments. i dont care too much about the variable naming conventions (camel case? i hardly know el case) so long as names with multiple words in them are readable, and itterators in loops can be single-letters
  3. dont be an asshole.
  4. no ai tooling.

i might be slow responding to pull requests, i specced into learning to reread my code rather than learning git

to do

  • admin tools (delete files, edit settings)
  • user tools (edit attribution, replace file???)
  • more color schemes? and a way for admins and users to pick them