During the application process, quite a few applicants were stuck at setting up the development environment for debci. I would like to improve the experience. At first, I used docker because I was more familiar with it. After finding an empty VagrantFile
in the repository, I decided to try something new and went with vagrant. Learned some shell script and user permissions during the process and the biggest find was to use the debian/contrib-stretch64
box rather than debian/stretch64
. The contrib version contains the guest addition stuff.
I worked on opening a self service section for users to requests tests themselves this week. Got stuck a little bit every step of the way, but not really stuck. Interesting finds that I would like to log:
public
directory to the file to be generated in public/data/.html
and add it to bin/debci-generate-html
layout.erb
if it exists, and you can change set :views, <PATH>
to change the default directory to store the erb filesforeman start
you have to add $stdout.sync = true
before the print runsSinatra::ContentFor
to seperate _javascript_ files into the templates, and create dummy functions in lib/debci/html.rb
for static file generation to workThis week, besides the Self Service section, I also tried fixing the search package part of the index page. Currently it just takes what the user inputs and redirect them to the page which may or may not exist.
Things I did or should log down for this week:
Build-Depends:
in debian/control
We discussed and decided to work on non-JS versions of the Self Service Section. With _javascript_ enabled, the UX will be more complicated which requires more time to generate the whole concept and I would like things to work first since it doesn't exist yet.
Cheers,