Update README.md to include a demo site or screenshots #15
Comments
|
Thank you @mindware! I haven't had much time for this recently and hope to circle back to it once I get the FedRAMP Guides (to SAP, SAR, and POA&M) drafted. I'll certainly update the readme, plus I might have some updates to push soon. |
|
Hi, II tried to install in docker but there are some errors when I launched bat file. Is it possible to share the steps on how to install it, please? |
|
@garik-pilot: A colleague created that for me, and has a quirk. I didn't realize it was still in the repo. I fixed it on my system, but haven't made it so it works on any system yet. Here's the manual fix: First, if you are new to Docker you have to make sure it is configured for file sharing (Settings, Resources, File Sharing). Make sure to share the drive with your clone of the repo. Then, find and delete the "$PWD" in the batch file - delete the enclosing quotes too. They are part of the problem. Then put in the Linux-style path to your clone of the repo. My Git repos are all in D:\GitRepos, so for me, the line ended up looking like this: As I mentioned in my previous comment, I hope to circle back to this work next month, with some great updates in mind. On my to-do list is to fix the Docker command so it works for everyone without modification. |
|
Thanks!
…On Fri., May 22, 2020, 1:28 p.m. Brian Ruf, ***@***.***> wrote:
@garik-pilot <https://github.com/garik-pilot>: A colleague created that
for me, and has a quirk. I didn't realize it was still in the repo. I fixed
it on my system, but haven't made it so it works on any system yet. Here's
the manual fix:
First, if you are new to Docker you have to make sure it is configured for
file sharing (Settings, Resources, File Sharing). Make sure to share the
drive with your clone of the repo.
Then, find and delete the "$PWD" in the batch file - delete the enclosing
quotes too. They are part of the problem.
Then put in the Linux-style path to your close of the repo. My Git repos
are all in D:\GitRepos, so for me, the line ended up looking like this:
docker run -p 80:8080 -v "/d/GitRepos/OSCAL-GUI/webroot":/var/www/html trafex/alpine-nginx-php7
As I mentioned in my previous comment, I hope to circle back to this work
next month, with some great updates in mind. On my to-do list is to fix the
Docker command so it works for everyone without modification.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#15 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADEMGPSMTB45UIZ4FZJL57DRS2Y2LANCNFSM4M224LOA>
.
|
|
Brian,
I followed the steps as above and it seems like the nginx and php both
RUNNING but I can use GUI? I tried to open it as "localhost:8080/" or
"localhost:8080/OSCAL-GUI" or "GUI" but no luck. Could you share a url,
please?
…On Fri, May 22, 2020 at 1:28 PM Brian Ruf ***@***.***> wrote:
@garik-pilot <https://github.com/garik-pilot>: A colleague created that
for me, and has a quirk. I didn't realize it was still in the repo. I fixed
it on my system, but haven't made it so it works on any system yet. Here's
the manual fix:
First, if you are new to Docker you have to make sure it is configured for
file sharing (Settings, Resources, File Sharing). Make sure to share the
drive with your clone of the repo.
Then, find and delete the "$PWD" in the batch file - delete the enclosing
quotes too. They are part of the problem.
Then put in the Linux-style path to your close of the repo. My Git repos
are all in D:\GitRepos, so for me, the line ended up looking like this:
docker run -p 80:8080 -v "/d/GitRepos/OSCAL-GUI/webroot":/var/www/html trafex/alpine-nginx-php7
As I mentioned in my previous comment, I hope to circle back to this work
next month, with some great updates in mind. On my to-do list is to fix the
Docker command so it works for everyone without modification.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#15 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADEMGPSMTB45UIZ4FZJL57DRS2Y2LANCNFSM4M224LOA>
.
|
|
@garik-pilot - That's great! |
|
I use my bank laptop :) that doesn't allow to connect to local port 80. Is
there any way to launch it on another port?
I have another question. I am struggling to understand how to develop xsl
transform to filter/extract a specific group or control from
nist800-53v4.xml catalog to output in xml file. My final goal is to develop
xsl transformation to be able to make xml file that can be imported/used in
Archimate to create security layer.
Is there any basic tutorial (or may be a couple of example) to start from?
I used the generic xsl files and data transformation of other projects that
works but it seems to me I need to use some special keywords are linked to
oscal namespace.
I am really interesting to be engaged in this project (as security
architect in the bank) but I very junior in Oscal and xml transformation
right know (even having good development background in Java). I know the
basics of XPath and xslt but this is new area for me.
Thanks.
…On Fri, May 22, 2020 at 4:54 PM Brian Ruf ***@***.***> wrote:
@garik-pilot <https://github.com/garik-pilot> - That's great!
It should be running on port 80, not 8080, and it should just be right at
the root of localhost.
http://localhost
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#15 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADEMGPWL4AR3JX3MYO5C2RLRS3RBFANCNFSM4M224LOA>
.
|
|
@garik-pilot, I think you can just change the "80" in the command line to whatever port you can use. As for XSLT, I'm still somewhat new to it myself and have benefited from working with an expert on the NIST OSCAL team. I've dabbled a little, plus had him get me started with a few transforms. There is some early work HERE, but it likely needs some tweaking to work with the latest syntax. One goal I have for the GUI is to have a folder with XSLT files in it. Anytime I add another file (with the right metadata), the GUI will include it in the menu item, and process the appropriate OSCAL files with it. This feature was partially drafted when I needed to stop working on the GUI. NIST has published a draft XSLT for resolving profiles. They are working out a few minor glitches, but I plan to adopt that in the GUI for profile resolution using the above modular XSLT capability. As for tutorials, I tend to do a search and try a few to see which is working best for me. Finally, out of respect for the person who opened this issue about updating the README, can you open a second issue with any more questions, so he doesn't continue to get notifications of our conversation, or look for me on Gitter. |
|
sorry about that. thanks for your quick responses and great answers!
…On Fri, May 22, 2020 at 6:34 PM Brian Ruf ***@***.***> wrote:
@garik-pilot <https://github.com/garik-pilot>, I think you can just
change the "80" in the command line to whatever port you can use.
In other words, it might be something like this:
docker run -p 8888:8080 -v "/d/GitRepos/OSCAL-GUI/webroot":/var/www/html trafex/alpine-nginx-php7
As for XSLT, I'm still somewhat new to it myself and have benefited from
working with an expert on the NIST OSCAL team. I've dabbled a little, plus
had him get me started with a few transforms. There is some early work
HERE
<https://github.com/brianrufgsa/OSCAL-GUI/tree/master/webroot/oscal/HOLD%202019-08-27>,
but it likely needs some tweaking to work with the latest syntax.
One goal I have for the GUI is to have a folder with XSLT files in it.
Anytime I add another file (with the right metadata), the GUI will include
it in the menu item, and process the appropriate OSCAL files with it. This
feature was partially drafted when I needed to stop working on the GUI.
NIST has published a draft XSLT for resolving profiles
<https://github.com/usnistgov/OSCAL/tree/master/src/specifications/profile-resolution>.
They are working out a few minor glitches, but I plan to adopt that in the
GUI for profile resolution using the above modular XSLT capability.
As for tutorials, I tend to do a search and try a few to see which is
working best for me.
Here are a few I've looked at in the past:
https://www.w3schools.com/xml/xml_xslt.asp
Finally, out of respect for the person who opened this issue about
updating the README, can you open a second issue with any more questions,
so he doesn't continue to get notifications of our conversation, or look
for me on Gitter.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#15 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADEMGPTJGLIPENLS5VLR6FLRS34YFANCNFSM4M224LOA>
.
|
Understanding the project initially is a little difficult
The README is helpful but I'm not 100% sure what the project looks like coming in for the first time.
Improving README.md with helpful content
Providing a link to a live demo site or screenshots of the system and basic capabilities would be very helpful to increase adoption and participation.
The text was updated successfully, but these errors were encountered: