theforeman / theforeman.org Goto Github PK
View Code? Open in Web Editor NEWThe new and improved Foreman website.
Home Page: https://theforeman.org/
License: Other
The new and improved Foreman website.
Home Page: https://theforeman.org/
License: Other
http://theforeman.org/manuals/1.7/index.html#4.3SmartProxies should include a subsection about templates handling with an example configuration file and so forth. @dustints would you mind to do it since you wrote the feature?
Apart of the contribution.md, there is no mention of any license.
Is it implied that the theforeman.org is also part of the project and should be treated as GPL too ?
Would it be possible to have a license.md with the relevant license in it ?
Usual stuff:
1.9 specifics:
The bs-docs-sidebar doesn't scroll with the page. I suppose that's intentional, but on my Macbook Air this results in the scrollbar going off the screen and being unable to navigate to longer sections of the document:
Ostensibly, the "affix" attribute is supposed to fix this, but this didn't work when I tried it myself, but admittedly, my web design skills peaked around the time the blink tag was fashionable.
The first answer on this stackoverflow thread looks like the right direction:
When trying to install from source as described in http://theforeman.org/manuals/1.2/index.html#3.4InstallFromSource the bundle install fails with:
# bundle install --without mysql mysql2 postgresql test --path vendor
Unfortunately, a fatal error has occurred. Please see the Bundler troubleshooting documentation at http://bit.ly/bundler-issues.
Thanks!
/opt/foreman/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/1.9.1/psych.rb:297:in `initialize': No such file or directory - /opt/foreman/foreman-1.2.2/config/settings.yaml (Errno::ENOENT)
from /opt/foreman/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/1.9.1/psych.rb:297:in `open'
from /opt/foreman/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/1.9.1/psych.rb:297:in `load_file'
from /opt/foreman/foreman-1.2.2/config/settings.rb:3:in `<top (required)>'
from /opt/foreman/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/site_ruby/1.9.1/rubygems/core_ext/kernel_require.rb:53:in `require'
from /opt/foreman/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/site_ruby/1.9.1/rubygems/core_ext/kernel_require.rb:53:in `require'
from /opt/foreman/foreman-1.2.2/Gemfile:1:in `eval_gemfile'
from /opt/foreman/.rvm/gems/ruby-1.9.3-p448@global/gems/bundler-1.3.5/lib/bundler/dsl.rb:30:in `instance_eval'
from /opt/foreman/.rvm/gems/ruby-1.9.3-p448@global/gems/bundler-1.3.5/lib/bundler/dsl.rb:30:in `eval_gemfile'
from /opt/foreman/.rvm/gems/ruby-1.9.3-p448@global/gems/bundler-1.3.5/lib/bundler/dsl.rb:9:in `evaluate'
from /opt/foreman/.rvm/gems/ruby-1.9.3-p448@global/gems/bundler-1.3.5/lib/bundler/definition.rb:19:in `build'
from /opt/foreman/.rvm/gems/ruby-1.9.3-p448@global/gems/bundler-1.3.5/lib/bundler.rb:148:in `definition'
from /opt/foreman/.rvm/gems/ruby-1.9.3-p448@global/gems/bundler-1.3.5/lib/bundler/cli.rb:245:in `install'
from /opt/foreman/.rvm/gems/ruby-1.9.3-p448@global/gems/bundler-1.3.5/lib/bundler/vendor/thor/task.rb:27:in `run'
from /opt/foreman/.rvm/gems/ruby-1.9.3-p448@global/gems/bundler-1.3.5/lib/bundler/vendor/thor/invocation.rb:120:in `invoke_task'
from /opt/foreman/.rvm/gems/ruby-1.9.3-p448@global/gems/bundler-1.3.5/lib/bundler/vendor/thor.rb:344:in `dispatch'
from /opt/foreman/.rvm/gems/ruby-1.9.3-p448@global/gems/bundler-1.3.5/lib/bundler/vendor/thor/base.rb:434:in `start'
from /opt/foreman/.rvm/gems/ruby-1.9.3-p448@global/gems/bundler-1.3.5/bin/bundle:20:in `block in <top (required)>'
from /opt/foreman/.rvm/gems/ruby-1.9.3-p448@global/gems/bundler-1.3.5/lib/bundler/friendly_errors.rb:3:in `with_friendly_errors'
from /opt/foreman/.rvm/gems/ruby-1.9.3-p448@global/gems/bundler-1.3.5/bin/bundle:20:in `<top (required)>'
from /opt/foreman/.rvm/gems/ruby-1.9.3-p448@global/bin/bundle:23:in `load'
from /opt/foreman/.rvm/gems/ruby-1.9.3-p448@global/bin/bundle:23:in `<main>'
from /opt/foreman/.rvm/gems/ruby-1.9.3-p448/bin/ruby_executable_hooks:15:in `eval'
from /opt/foreman/.rvm/gems/ruby-1.9.3-p448/bin/ruby_executable_hooks:15:in `<main>'
It seems to be necessary to copy the configuration files before doing the install.
Also the example makes no sense since it states the bundle install should be run like this:
bundle install --without mysql mysql2 sqlite test --path vendor
but the stated config/database.yml.example uses a sqlite database. Therefore a hint would be nice either to change the db config or providing the correct set that should not be used.
Tasks:
The smart proxy section (4.3) and probably the plugins section (6) should have information about smart proxy plugins, how they add extra config files, how to enable them etc and how they're packaged.
The 1.10 notes should get a warning because it is the last release that will get puppet 2.7.0 support in the installer.
Visit http://theforeman.org/manuals/1.8/index.html#Releasenotesfor1.8 and click one of the YouTube video icons on the right hand side. This should open up a modal with the video embedded, but instead the page greys out and no video is displayed.
The API docs are currently out of date, they're built on 1.6 or thereabouts I think.
The following packages have unmet dependencies:
ruby-kafo-parsers : Depends: ruby-rdoc (>= 3.12.0) but it is not going to be installed
E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution).
I had to do dpkg --purge ruby-kafo-parsers ruby-kafo to be able to use apt again. Dependency hell?
Usual stuff:
1.11 specifics:
@abenari could we change the link colour to something like #34799d? I'm struggling to notice links in the manual since the redesign and am worried readers will miss them.
The manuals should have edit icons next to each section to invite readers to submit fixes back to this repository via a PR.
Section 4.3.4 documented the built-in Chef support in Smart Proxy 1.6 and earlier, but it was moved to smart_proxy_chef in 1.7.
This section should be moved to plugin-specific documentation (like Discovery).
The website used to have the latest version displayed clearly on the home page, but this was lost during #274.
The partial is still there at _includes/social.html and I'm regularly updating it, it just needs fitting into the new design somewhere. Perhaps under the two buttons on the homepage?
Foreman 1.8 supports provisioning of CoreOS, which should be added to the website and manual.
http://projects.theforeman.org/issues/7652
https://github.com/theforeman/community-templates/tree/master/coreos
The way some compute resources (Openstack, EC2...) create a key pair is currently very obscure for the user. The process should be documented, especially since it stores the secret key on the database and it's not retrievable in any way by any user other than people with access to the Foreman database.
As jekyll 3 is approaching (see github/pages-gem#175) we should care about it. With the following diff, the site is building again, but there are some glitches, so this is just to raise awareness for now.
diff --git a/_config.yml b/_config.yml
index cda5e03..f296337 100644
--- a/_config.yml
+++ b/_config.yml
@@ -18,7 +18,7 @@ blogdesc: News, notes and noise from around the Foreman community
safe: false
future: false
-highlighter: pygments
+highlighter: rouge
markdown: rdiscount
navigation:
@@ -35,3 +35,5 @@ navigation:
gems:
- jekyll-feed
+ - jekyll-gist
+ - jekyll-paginate
The section "Updating API Auto-Generated Docs by apipie" does not show link breaks. I thought markdown automatically does this.
_includes/manuals/1.8/1.2_release_notes.md line 69 has references to plugins, Chef, Salt, and the index. These links do not seem to be working.
Work in progress:
Since the last redesign, the website is missing a link to blog.theforeman.org or /blog.html.
A description of how inherited organisations/locations work should be added - in fact, we're missing multi-org entirely from the manual. In particular how the views and permitted assignments work.
Work in progress:
There should at least be a link to the blog on the foreman home page. It would be beter to have links to the X(=3?) latest articles as well.
Usual stuff:
1.10 specifics:
The host group inheritance features (#9591) during host creation added in Foreman 1.10 should be described in the manual, probably around section 4.4 (Provisioning). It should explain how attributes are copied from a group on host creation and that they can be inherited, changed explicitly or unset explicitly.
_includes/manuals/1.2/3.5.5_importing_facts.md
Refers to this script https://github.com/theforeman/puppet-foreman/blob/283619064fbde0275235535b19c53da249357035/files/push_facts.rb which was deleted.
The script needs to be updated to include the CA file and certs or the docs need to be updated to explain how to do it without the script.
$foreman_ssl_ca = "/var/lib/puppet/ssl/certs/ca.pem"
$foreman_ssl_cert = "/var/lib/puppet/ssl/certs/<fqdn>.pem"
$foreman_ssl_key = "/var/lib/puppet/ssl/private_keys/<fqdn>.pem"
And at the http part
http.ca_file = $foreman_ssl_ca
http.cert = OpenSSL::X509::Certificate.new(File.read($foreman_ssl_cert))
http.key = OpenSSL::PKey::RSA.new(File.read($foreman_ssl_key), nil)
Thanks,
William
A new section, perhaps 4.9 Monitoring in 4. General Foreman should be added to describe the global statuses and substatuses feature added in Foreman 1.10.
It should show that each host has multiple statuses shown on its own host page, and this is combined into a global status shown on the host list. The APIs show this too, with individual statuses and a global status.
The upgrade section (3.6) for Foreman 1.10 and the RPM packages section (3.3.1) should state that EL installations with Hammer only now also require SCL packages to be available. Previously they only needed EPEL.
Some of the pandoc-converted blogs are a mess, we should clean them up a bit
I get the following error on Ubuntu Trusty
[ERROR 2014-06-04 08:09:59 verbose] /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[homesystem.rabbithole]: Could not evaluate: undefined method `find' for #String:0x000000051f5928
There are no other errors and the web dashboard seems to work fine. Clues?
Browsing the Foreman API is tough after the site redesign. The 1.8.0 announcement takes up too much screen space.
Browser: Chrome 42.0.2311.90
URL: http://www.theforeman.org/api_v2.html
Screenshots:
restrict_registered_puppetmasters
and require_ssl_puppetmasters
are now restrict_registered_smart_proxies
, and require_ssl_smart_proxies
, respectivelyPerhaps part of section 4.4 (provisioning), but some detail around SLES provisioning (#3733) would be good.
When using the "Run Puppet" button on hosts in Foreman, under the mco provider, it will send the command to mco with a lower case fqdn and will then fail to find it:
mco ping:
Ultralisk time=104.35 ms
Command as it comes in from foreman:
[root@puppet etc]# /usr/bin/mco puppet runonce -I ultralisk No request sent, we did not discover any nodes.
but if you manually run it with the correct case it works fine.
The documentation for the API refers to Foreman 1.3.
I did finally notice the 'optional' section after logging into IRC, but perhaps in section 2.1 you can say 'you can now discover hosts skip section 2.2 unless you have a locked down environment.'.
The API v2 section (5.1) should document the format of error responses that the API will generate (the JSON objects with messages etc).
Being worked on in _includes/manuals/1.5/.
Tasks:
Perhaps part of section 4.4 (provisioning), but some detail around FreeBSD provisioning and its requirements (#2572) would be good.
The Hammer "success story" in section 4.5.2 needs updating as some of the arguments have been improved, e.g. using names instead of IDs.
I'd also like to see improved formatting and explanations of the commands.
The manual (as of version 1.5.2) instructs you to start the installation on a Debian system by runnning the following commands:
echo "deb http://deb.theforeman.org/ wheezy 1.5" > /etc/apt/sources.list.d/foreman.list
echo "deb http://deb.theforeman.org/ plugins 1.5" >> /etc/apt/sources.list.d/foreman.list
wget -q http://deb.theforeman.org/pubkey.gpg -O- | apt-key add -
apt-get update && apt-get install foreman-installer
Notice how the signing key is downloaded through plain HTTP. Simply replacing http with https in the URL doesn't work: strangely I don't even get a server error, just no response at all. The key has to be available from a secure source to even be useful at all, otherwise you can be MITM-ed and never notice any errors or failures.
The settings list in section 3.5.2 is out of date as of Foreman 1.10 where new settings were added.
Settings also now have a friendly name which is displayed in the UI in preference to the underscored name used in the DB and settings.yaml.
It should just be a question of adding btn btn-foreman-blue
to the pagination class, but something is interfering with the background.
the site seems to be down
To avoid people making the same silly mistake enabling GCE as a compute resource can I suggest the documentation for 5.2.4 Google Compute Engine Notes be updated from
"Requires client e-mail address and p12 certificate file to access"
to
Requires client e-mail address of an authorised google cloud console client ID is entered in the new compute resource screen and the .p12 certificate file is stored on the foreman server in a location the foreman user account has permission to read
Foreman 1.8 supports using user-data templates in cloud-init style, which are interpreted by Fog into customization templates for VMware. This should be documented in 5.2.
http://projects.theforeman.org/issues/8601
Unfortunately it appears it may not work: https://groups.google.com/forum/#!topic/foreman-dev/Lsfw9CunyzA
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.