I'm working on serving the doxygen documentation for our C++ project on readthedocs so it gets built automatically and documentation for all versions is available.
I'm using doxyrest to convert doxygen XML output to RST and this build fine both on my local machine and on readthedocs but, while I can download the pdf and the zipped html versions of the documentation off readthedocs, I just get the maze thing when I try and read it online.
Here is my docs directory
Turns out this happens if your conf.py is in docs/ rather than docs/source
Related
I was interested on on Google's web app-Shell. I've downloaded it GitHub. But I found that there is no index.html/index.php file in the whole code. All I mainly found, is the licence file, app.yaml file and app.js file. Link to that page, is here.
I heard,that I can install the project in my web hosting site, by using terminal. But terminal is not an option for my situation. I've stopped using Firebase, because I must have terminal for it. So, is there any other idea to install the project in my website?
Can I have a flat file, so that I could simply past the html,css, JavaScript and other media files into my server?
Unfortunately the Google web app-Shell isn't designed to have an index.html file. There is a views folder that has what you're looking for https://github.com/GoogleChromeLabs/application-shell/tree/master/server/views.
As we can see they're using handlebars for as a templating system. For example, if we look at https://github.com/GoogleChromeLabs/application-shell/blob/master/server/views/layouts/default.handlebars we can see that they have {{> open-page}} and {{{body}}}. If we look at handlebars documentation these partials are rendered into other views.
Essentially, there isn't a single index.html we can point to, but we can reconstruct the app by exploring their views.
After using the Polymer CLI, there is a generated polymer.json file. I'm having a hard time Googling/finding information on what this file is used for and how. Can someone explain how this file affects my application?
I found all the answers in the docs eventually.
https://www.polymer-project.org/1.0/docs/tools/polymer-cli
polymer.json is a config file that lets you specify your build entrypoint, shell, and fragments, rather than having to pass these in as command-line flags to polymer build.
The Build configuration file section from the Polymer CLI guide talks specifically about polymer.json. The Serve your app doc from the App Toolbox docs also has some good information for understanding how Polymer CLI builds projects.
The source for my Jekyll-powered website lives in a git repo, but the website also needs to have a couple large static files that are too large to go under version control. Thus, they are not part of the Jekyll build pipeline.
I would like for these to simply live in an assets directory in the Jekyll destination (which is a server directory; note that I don't have have any control over the server here; all I can do is dump static files into a designated directory) that does not exist in the git repo. But, running jekyll build deletes everything in the output directory.
Is there a way to change Jekyll's behavior in this case? Or is there some other good way to handle this issue?
Not sure this addresses the specific case in the OP, but seeing as how I kept getting to this page when I finally found an answer here, I thought I'd add an answer to this question in case it helps others.
I have a git post-hook that builds my jekyll site in my webhost when I push to my host, but it was also deleting anything else that I had FTP'ed over. So now I've put anything I need to stick around in a directory (external/ in my case), and added the following to my _config.yml:
exclude: [external]
keep_files: [external]
and now files in external/ survive.
If you upload Jekyll's output directory via FTP to your server, you can use a FTP tool that lets you ignore folders.
For example, my own site is built with Jekyll, but hosted on my own webspace, so I'm uploading it via FTP.
I explained in this answer how I scripted the building and uploading process, so I can update my site with a single click.
In my case (Windows), I used WinSCP, a free command-line FTP client, for this.
If you're not on Windows, you need to use something else, but there are probably other FTP tools out there that are able to ignore folders.
To ignore your assets folder in WinSCP, you just need to put this line into the script file:
(the file which contains the actual WinSCP commands - read my other answer for more information)
option exclude "assets/"
Now you can upload your large assets folder on the server once, and it won't be overwritten/deleted when you later update your site via FTP.
does anyone know if it is possible to set the working directory for running the application you create in monodevelop?
The app is written to the bin/Debug directory and that seems to be the working directory when you debug the application. For my application (which I am porting from Windows) it takes an XML configuration file which references other XML files, the paths (in the configuration xml) I use are relative paths (which is sensible imo).
IIRC Visual Studio lets you set the working directory when you are debugging, does monodevelop? I had a good look around the options and tried to search for an answer, but no luck.
thanks
Dave
As far as I'm aware "Run" and "Debug" mode use the same working directory.
Have a look at the following post
Hi i'm installing extensions by programmatically by a little c# program.
I just did see the software doesn't work on my friend.
i did see his chrome directory is not at %appdata% folder its at program files?
so how to find the real latest version of chrome directory for install plugins?
Google says
Windows:
chrome_root\Application\chrome_version\Extensions\
Example: c:\Users\Me\AppData\Local\Google\Chrome\Application\6.0.422.0\Extensions\
but how to find the chrome_root?
Visit chrome://version.
Look at Profile Path.
Extensions can be found in the Extensions subdirectory of the path you found at the previous step.
You can also load the extension using the --load-extension flag:
chrome.exe --load-extension=path/to/extension
The recommended mechanism for installing extensions programmatically is external extensions. It has the advantage of not depending on Chrome paths that might change, instead you can use a stable registry key or JSON file.