http://packages.synocommunity.com down ?

[dutchdude1966]

Hi it seems http://packages.synocommunity.com is not available !

Greeting Bart

[Dr-Bean]

@simwah Wait and see. Should be fine, as long as the packages have not been edited for some reason.

[Dr-Bean]

@Diaoul Done with de19253ce59ede1f67c45e9bdf787b6d39d727af then.

[Robpollard]

I've downloaded the x86-spk of Python for my DS412+ but got a package error (from: https://www.dropbox.com/sh/aiz3migoap42b7s/AABHlfR7fvQGr8VwBat-xgyWa) - did I download the wrong spk? If yes, which one should I take? Btw, for future reference for those who want to know which CPU they have: http://forum.synology.com/wiki/index.php/What_kind_of_CPU_does_my_NAS_have

Edit: Thank you very much, Dr-Bean!

[Dr-Bean]

@Robpollard I suggest to use this link to determine the correct arch: https://github.com/SynoCommunity/spksrc/wiki/Architecture-per-Synology-model. For 412+, you should use the cedarview arch.

A couple of generic warnings for good measure:

• Downloading SPKs from outside the official repository has two risks:
  • There's no way for us to guarantee that those packages have not been tampered with;
  • Packages that are built directly from the github code can be beta or unstable.
• If the Python 2.7.6-8 package was built recently, it only works on DSM5. This limitation might apply to some other packages too, although that is an unknown at this point.

[FluffBunny]

@wouter0100 Thanks for the access to the packages, much appreciated. If you could also add the Pytho packes as @Diaoul requested you are in epic god mode and i wil kneel for you!

Anyway thanks to everyone who is making the repository possible and working there ass off!

[Wouter0100]

@FluffBunny When I'm home I will try to build one :) Unfortunately the last time the build of Python was that long...

[FluffBunny]

@wouter0100 Haha see what you can do as there is a lot to build if I understand correctly (synology noob here)... So if it is too much work too bad, we will have to wait till repo is back. But if you are gonna try one try the evansport arch one, gna gna. No serious, thanks for even considering it.

Quote Dr-Bean: "Btw, this time, you might want to add the Python packages too. However, there's a catch: there are two versions, one for DSM4, one for DSM5 (for each arch, obviously). Would it be possible for you to cover that?"

[Dr-Bean]

@FluffBunny @wouter0100 In itself, the building process of Python is not an issue, it just takes time to compile the package. Takes me (on a fairly slow VM, that is) about 45 mins per build, times 13 arches, times 2 for DSM4 and DSM5. Adds up to about 20 hours total.

Now that I'm thinking of it, we could get away with just the DSM4 builds, since those work on DSM5 too...the other way around won't.

[Diaoul]

@SynoCommunity/developers: Should we drop support for DSM < 4.2 ? It could save some trouble with the repo. If I'm not mistaken that means only models x08 and x07 so that's 6yo+ models.

[bru7us]

Sounds reasonable - however if there are packages that will still run fine on earlier DSM versions, it would be good to have them remain available for direct download and statically linked in an "Archive" page on the front end site.

[Dr-Bean]

Yep, agree with both of you. Ultimately, providing backwards compatible packages will prevent us from using new development features. However, if we still can build certain packages for earlier DSM versions, direct download would be nice.

[Diaoul]

ETA is 1-2 days

[Diaoul]

New front page online. Suggestions on design/content are welcome, still working on the backend.

[bru7us]

Looks good (and even has a favicon)! A couple of points of feedback:

• "Easy Install" and "Bleeding Edge" are titles so should have capitalization (both under the icons and where they are headers)
• Missing word under "Easy install": Once our repository is added
• Rephrase under "Bleeding edge": Our packages are aim to be compatible with the latest version...
• Should you add trademark notation for 'Synology' and 'DSM'?

I was also going to comment about linking to the spksrc contributors, but then I spotted your TODO commented out in the source. :)

[GldRush98]

I think you have a typo in the url under step 2:

Click Add, type SynoCommunity as Name and http://packages.packages.synocommunity.com/ as Location and then press OK to validate.

You've doubled up packages there I believe.

[ragnarnz]

@GldRush98

To add to this, if you then browse to http://packages.packages.synocommunity.com/ in a browser, Step 2 under easy install will then read 'http://packages.packages.packages.synocommunity.com/'

[GldRush98]

Ah, it's dynamically generating it causing the funkiness.

[jb510]

@Diaoul - humble suggestion, add a "Website" label to the github issue tracker to help track issues on the new site (or a stand alone repo of the web site)

 *Step 2*
 Click Add, type SynoCommunity as Name and http://packages.synocommunity.com/ as Location and then press OK to validate.

is generating the url based on a wierd relative path. So we're seeing, http://packages.{current_url} http://packages.www.synocommunity.com/ http://packages.packages.synocommunity.com/ etc...

[bru7us]

@jb510 see https://github.com/SynoCommunity/spkrepo for issues on the site/repo side.

[jb510]

@bru7us I assumed that repo was either dead or for the package server (not the website). In the future I'll post issues with the website there. Thanks.

[Diaoul]

Thanks for your feedback. I've done the appropriate changes locally. I've automated deployment too (using fabric) to make pushing changes in production easier.

The current front page's text is really a placeholder until I or anybody comes up with something better. I think the 3 sections are defining SynoCommunity correctly. Suggestions are welcome!

There is still work to do on the package side even though the database schema is done and the json output for the package center nearly functional. Database feeding from SPK file must be addressed as well as thumbnails and screenshot file management. I am working on it.

I am confident I can get it done by the end of the week. The code will be released under MIT license as soon as the core is functional. (frontend + package upload / download).

[Diaoul]

@jb510: what do you mean by a website label? We can add a GitHub logo so it's more eye catchy. Also, the text-muted or the small tag could be used in the headers such as: Easy Install. [text-muted]My grandma could do it[/text-muted] Depends on what. About the auto generated urls, I'll restrict the website to be on http://synocommunity.com/

[jb510]

I meant in this issue tracker, (ie. currently this issue is labeled bug, repo). But if you're not using this repo for the website, don't bother. Just refer website related issues over to spkrepo

[Robpollard]

I just donated 5 euros, thank you for all your hard work, may we all enjoy the SynoCommunity for many years hence.

[bru7us]

@Diaoul , probably worth ensuring there's a www. redirect as well as the root domain.

[Diaoul]

@bru7us: there's a wildcard subdomain CNAME on the DNS, I need to dig nginx and flask documentation for proper handing of domains.

[bru7us]

Yeah I was just responding to your previous comment saying that you'd just restrict the site to be on the root domain only. To that I say, root domain plus the www. sub-domain (after you remove the wildcard).

[bitking]

@Diaoul Thanks dude, just donated 5,- for your work! keep it up!

[grimrod42]

Any word, last was 1-2 days on Thursday...

[potyt]

Si senor, me mucho wanto

[alfsoft]

Hello! Just noticed that Error 404 occurs when navigating to main page with "www" in URL. http://www.synocommunity.com/ - Error http://synocommunity.com/ - Normal

[Diaoul]

I'm working on the API, re-upload of packages will be necessary. Also I've made some changes to improve maintainability. Now the package revision is renamed package build and should be unique per package name, architecture and firmware.

I'm still confident it'll be done by the end of the week.

[Dr-Bean]

@Diaoul Nice :) Btw, are the packages from the old repo still available, or would those have to be recompiled? Mainly interested because of 4.3 toolchains/DSM4.x compatibility.

[jaysont000]

@Diaoul Donated 5 Euros, thanks for the work!

[mlaeng]

Just fyi:

If browse to packages.synocommunity.com I get this:

Bad Request The browser (or proxy) sent a request that this server could not understand.

Synology says: Invalid location.

[Diaoul]

Status:

• Spent more time than expected on the query to support multiple DSM firmware versions but that's done
• Package upload fills correctly the database
• Code is visible by all SynoCommunity developers
• Burnt my left thumb with boiling soup

Todo before release:

• Secure package uploads with authentication
• Save pictures of packages
• Save uploaded package

Todo:

• Developer registration
• Link to github using API
• One page per developer
• Page with package list overview
• One page per package
• Support for screenshots

[hazcod]

Will we have to manually compile syn. versions of packages and upload them? I'd love to help/compile, but this means that for example that if I upload a newer version than the current package on synocommunity, this will be a 'different' package? Or will it come under the generic package name?

Keep up the good work!

[unorig]

Didn't know how much I needed synocommunity until it was down.

Donated 25 euros. I encourage anyone else that has left a comment to do the same.

[mcgroarty]

Donated as well. Get well soon, website!

[grimrod42]

I just donated 10e as well, good luck getting it backup soon

[Diaoul]

Thanks for your support.

This is a new server side application that I develop, it'll allow us to manage packages more efficiently and also supports new features. From a user side, it'll be nicer and easier.

I want to get things right because it's harder to amend when everything is up and running. We're getting close.

[ddfamily]

I had to reinstall from scratch my Synology, and noticed Synocommunity was down!!! Awful nightmare... I donated 10e for your great work. Keep up the good work and get it back up. We need you!!!

[unorig]

Good work @mcgroarty and @grimrod42. Doesnt matter how much. Its good to show your appreciation and support!

[unorig]

Well done @ddfamily - good to see people get behind these guys.

[koppelbakje]

@ddfamily same situation for me, as well as the 10e donation. Keep up the good work!

[TweekDash]

donated €20.00 EUR too thanks so much for your work! i have two friends buying synologys this week hope the site is back up so i can help load their systems with packages :)

[potyt]

You take bitcoin?

There's probably an incentive to not get it up too quickly right now, making hay while it's down!

[Diaoul]

The code is open to all SynoCommunity's developers and contributions are welcome. I have a full time job and I do my best on my free time, I know it's taking long, it's a complete rewrite of the server side code with a lot of new features.

When it's back online it's for good. I won't do some quick'n'dirty fix.

[ddfamily]

Thanks Diaoul for your great work. Do you have an ETA for the server to be back online? Couple days, weeks or months?

[unorig]

Has anyone got a copy of any of the SPK packages by chance? I want to get Python, SickBeard, SABnzb.