Stuck at a certain part

241 views
Skip to first unread message

djjohn...@gmail.com

unread,
Jan 31, 2017, 1:32:49 AM1/31/17
to glazier-discuss
So, I sifted through the code and added the modules required in order to run it but I'm stuck at the version-info.yaml and other yaml files specified in the code. Seems the templates to these files aren't provided so I'm not too sure how the web structure should completely look like.

Steps Taken:

A: Modules used, replaced fakefs with pyfakefs:

  1. git clone https://github.com/google/python-gflags.git
    1. This is done in any directory
    2. cd into directory and run: python .\setup.py install
  2. git clone https://github.com/yaml/pyyaml.git
    1. This is done in any directory
    2. cd into directory and run: python .\setup.py install
  3. git clone https://github.com/google/winops.git
    1. copy 'gwinpy' directory into the same directory 'glazier' is in
    2. do not copy into the 'glazier' directory
  4. git clone https://github.com/jmcgeheeiv/pyfakefs.git
    1. This is done in any directory
    2. cd into directory and run: python .\setup.py install
  5. git clone https://github.com/testing-cabal/mock.git
    1. This is done in any directory
    2. cd into directory and run: python .\setup.py install
  6. git clone https://github.com/aliles/funcsigs.git
    1. This is done in any directory
    2. cd into directory and run: python .\setup.py install
B: Then made the following edits:
  1. Switched all fakefs calls to pyfakefs
  2. Added a line 'flags.FLAGS(sys.argv)' to 'autobuild.py' as gflag errors were populating:
    1. flags.FLAGS(sys.argv)
      FLAGS = flags.FLAGS

C: I then populated a 'version-info.yaml' with random stuff in the root of apache for the code to pull down and read. Just not sure if I populated it correctly. By default I used what was in the 'autobuild_test.py'.

As stated, it would be nice to have template files to use since very little documentation if given. This way, I can just use those, tweak it to my needs and deploy as needed.

Example:

Web structure should look like this (forgive me, still trying to sift through code to understand). Possibly added to the Github in order for someone to just grab it and drop it into their apache/IS to use right away.:

  • www
    • version-info.yaml
    • bin/
      • blah.yaml
    • config/
      • blah.yaml
    • stable/
      • blah.yaml
    • unstable/
      • blah.yaml

Anywho, any direction on the yaml stuff would be great. I know you guys are still working on it, which is awesome! Just confused on what should live where and how should files look like.

Matt LaPlante

unread,
Jan 31, 2017, 1:46:57 PM1/31/17
to djjohn...@gmail.com, glazier-discuss
I've added some new documentation which may be of help. Let us know how it goes and we can add further detail from there.

https://github.com/google/glazier/blob/master/doc/setup/index.md

--
You received this message because you are subscribed to the Google Groups "glazier-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to glazier-discuss+unsubscribe@googlegroups.com.
To post to this group, send email to glazier-discuss@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/glazier-discuss/a55312c5-211a-4018-98f8-c076c5842701%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

duhoon...@gmail.com

unread,
Jan 3, 2019, 3:28:28 AM1/3/19
to glazier-discuss
Hi,

Struck in the same situation.

Documentation doesn't  provide much insight as to how to proceed on this.

Writing to check if you were able find the solution to this? 
Reply all
Reply to author
Forward
0 new messages