Nextcloud Server ☁
A safe home for all your data.
Why is this so awesome? ?
?Access your Data You can store your files, contacts, calendars and more on a server of your choosing.
?Sync your Data You keep your files, contacts, calendars and more synchronized amongst your devices.
?Share your Data …by giving others access to the stuff you want them to see or to collaborate with.
?Expandable with hundreds of Apps …like Calendar, Contacts, Mail, Video Chat and all those you can discover in our App Store
?Security with our encryption mechanisms, HackerOne bounty program and two-factor authentication.
You want to learn more about how you can use Nextcloud to access, share and protect your files, calendars, contacts, communication & more at home and at your organization? Learn about all our Features.
Get your Nextcloud ?
☑️Simply sign up at one of our providers either through our website or through the apps directly.
?Install a server by yourself on your own hardware or by using one of our ready to use appliances
? Buy one of the awesome devices coming with a preinstalled Nextcloud
? Find a service provider who hosts Nextcloud for you or your company
Enterprise? Public Sector or Education user? You may want to have a look into Nextcloud Enterprise provided by Nextcloud GmbH.
Get in touch ?
You can also get support for Nextcloud!
Join the team ?
There are many ways to contribute, of which development is only one! Find out how to get involved, including as translator, designer, tester, helping others and much more! ?
Development setup ??
?Set up your local development environment
?Pick a good first issue
?? Create a branch and make your changes. Remember to sign off your commits using git commit -sm “Your commit message”
⬆ Create a pull request and @mention the people from the issue to review
? Fix things that come up during review
? Wait for it to get merged!
Third-party components are handled as git submodules which have to be initialized first. So aside from the regular git checkout invoking git submodule update –init or a similar command is needed, for details see Git documentation.
Several apps that are included by default in regular releases such as First run wizard or Activity are missing in master and have to be installed manually by cloning them into the apps subfolder.
Otherwise, git checkouts can be handled the same as release archives, by using the stable* branches. Note they should never be used on production systems.
Working with front-end code ?
We are moving more and more towards using Vue.js in the frontend, starting with Settings. For building the code on changes, use these terminal commands in the root folder:
# install dependencies
# build for development
# build for development and watch edits
# build for production with minification
When making changes, also commit the compiled files!
We still use Handlebars templates some places in Files and Settings. We will replace these step-by-step with Vue.js, but in the meantime you need to compile them separately.
If you don’t have Handlebars installed yet, you can do it with this terminal command:
sudo npm install -g handlebars
Then inside the root folder of your local Nextcloud development installation, run this command in the terminal every time you changed a .handlebars file to compile it:
Before checking in JS changes, make sure to also build for production:
Then add the compiled files for committing.
To save some time, to only rebuild for a specific app, use the following and replace the module with the app name:
MODULE=user_status make build-js-production
Please note that if you used make build-js or make watch-js before, you’ll notice that a lot of files were marked as changed, so might need to clear the workspace first.
Working with back-end code ?
When changing back-end PHP code, in general no additional steps are needed before checking in.
However, if new files were created, you will need to run the following command to update the autoloader files:
After that, please also include the autoloader file changes in your commits.
Tools we use ?
? BrowserStack for cross-browser testing
? WAVE for accessibility testing
? Lighthouse for testing of performance, accessibility and more
Contribution guidelines ?
All contributions to this repository from June, 16 2016 on are considered to be
licensed under the AGPLv3 or any later version.
Nextcloud doesn’t require a CLA (Contributor License Agreement).
The copyright belongs to all the individual contributors. Therefore we recommend
that every contributor adds following line to the header of a file, if they
changed it substantially:
@copyright Copyright (c)
Please read the Code of Conduct. This document offers some guidance to ensure Nextcloud participants can cooperate effectively in a positive and inspiring atmosphere, and to explain how together we can strengthen and support each other.
Please review the guidelines for contributing to this repository.
More information how to contribute: https://nextcloud.com/contribute/