-
Notifications
You must be signed in to change notification settings - Fork 142
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Documentations update #772
Comments
Here is the section I made about multi monitor on fedora: I can change whatever in those docs. Just let me know what should be changed. |
FYI: I'm not actually paying for the domain. I believe that's @Lekensteyn ? |
Oh, OK. Yeah, I could host it too without problem, but it was more about the need to pay a domain name for nothing and also have a far easier way to handle site management. ;) |
Yes, I am paying for the .org domain, it is no problem. There was a git repo on the server for the web content, maybe we should put it on Bumblebee-Project/bumblebee-web? A post-commit hook could then somehow ping the server and trigger a pull. What about the tarballs? I did not check them in when creating the git repo, they are untracked by git, but must still be uploaded for releases. @Thulinma What is the SSH username? I tried peter, lekensteyn and bumblebee, but the key was rejected. |
What about using Github + Travis for the release tarballs? Free hosting and bandwidth, and doing a release is just the matter of pushing a git tag. If you guys want, I can look into it next week. |
@Lekensteyn I actually think that server doesn't allow logins for the bumblebee data at all right now. I probably forgot to add the user when moving hosts last year. I'll take a look tonight and will check. |
@bluca That’s a good idea. @Lekensteyn We could just use Bumblebee-Project/Bumblebee-Project to get the automated bumblebee-project.github.io website feature like proposed above. Likewise, the hook is really trivial, and with bluca proposal the release tarballs should be an easy thing. |
@gsgatlin I’m not sure what is the current status of multi-monitor in fact. The change I was referring to is the changes needed in xorg.conf.nvidia and 10-input-drivers.conf. |
Can somebody upload the website on github of http://bumblebee-project.org/ maybe adding a FAQ? |
@Danger89 I would upload it all to a organization page, but it appears I don't have the permissions required to create the repo for this. |
@Thulinma: You should have all rights now. ;) |
@ArchangeGabriel Thanks! Working now: https://bumblebee-project.github.io/ |
I'll change the CNAME, currently checking whether I can make this work with SSL. We need to:
This does not work for SSL though unless we put a proxy in between (like Cloudflare). I guess this is not much of an issue since it is not a "regression" from the previous situation? |
Just to be aware of things, does bumblebee team will pursue the development for 4.0? |
@rafaelcn There will be a 4.0, but at the moment it does not seem to be a high priority. |
Thanks for the info. I want to work with this piece of Bumblebee software as well :-) |
I see still quite a bit of views on the FB page of Bumblebee, while I do not post any update since there is nothing to tell. But still we have visits almost each day... Meaning Bumblebee is still searched on Google Confirms this via Google Trends. 'Bumblebee Linux' -> Blue vs 'Nvidia Prime' -> Red. |
With 4.0 on track, they are several documentation updates needed around there.
I’ll try to list them here, feel free to add other items. For now I see:
Also, we could make use of newer GitHub functions:
We may change http://bumblebee-project.org/ for bumblebee-project.github.io using https://help.github.com/categories/github-pages-basics/, so that @Thulinma could stop paying for the domain and having to host us.
The text was updated successfully, but these errors were encountered: