fedora-docs / docs-fp-o

Clone
Source Code
GIT

#73 Issue #20 - first step to move _images/404.html to root
Closed 6 years ago by bex. Opened 6 years ago by abitrolly.
fedora-docs/ abitrolly/docs-fp-o 404  into  master

file added
+135 
@@ -0,0 +1,135 @@ 
 

+ <!DOCTYPE html>
 

+ <html lang="en">
 

+   <head>
 

+     <meta charset="utf-8">
 

+     <meta http-equiv="X-UA-Compatible" content="IE=edge">
 

+     <meta name="viewport" content="width=device-width, initial-scale=1">
 

+     <!-- The above 3 meta tags *must* come first in the head; any other head content must come *after* these tags -->
 

+ 

+     <title>Fedora Documentation Website</title>
 

+ 

+     <!-- Bootstrap -->
 

+     <link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.5/css/bootstrap.min.css">
 

+     <link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.5/css/bootstrap-theme.min.css">
 

+ 

+     <link rel="stylesheet" href="https://overpass-30e2.kxcdn.com/overpass.css">
 

+     <link rel="stylesheet" href="_stylesheets/asciibinder.css">
 

+ 

+     <!-- HTML5 shim and Respond.js for IE8 support of HTML5 elements and media queries -->
 

+     <!-- WARNING: Respond.js doesn't work if you view the page via file:// -->
 

+     <!--[if lt IE 9]>
 

+       <script src="https://oss.maxcdn.com/html5shiv/3.7.2/html5shiv.min.js"></script>
 

+       <script src="https://oss.maxcdn.com/respond/1.4.2/respond.min.js"></script>
 

+     <![endif]-->
 

+   </head>
 

+   <body>
 

+     <div class="container">
 

+       <div class="row">
 

+         <div class="page-header">
 

+           <img src="/_images/fedora.svg" class="img-responsive" />
 

+           <h2><strong>Fedora Documentation Site</strong></h2>
 

+         </div>
 

+       </div>
 

+       <div class="row">
 

+         <div class="col-md-8">
 

+           <h4><strong>Fedora Documentation - 404 Page Not Found :(</strong></h4>
 

+           <p>Hi! You've arrived at Fedora documentation page which does not actually exist. This may be because you followed a link to an older document which has been retired. For reference, you can find those in our <a href="https://docs-old.fedoraproject.org/">old document archive</a>. Or, you can browse <a href="https://docs.fedoraproject.org/">current docs</a>.</p>
 

+           <p>It may also be that this page _should_ exist, but sadly does not. If this is the case, and you know what it should say, you can <a href="https://pagure.io/fedora-docs">contribute via the Docs Project</a>.</p>
 

+           </div>
 

+         </div>
 

+       </div>
 

+     </div>
 

+     <div id="bottom" class="text-muted py-3" >
 

+         <div class="foot">
 

+             <div class="container">
 

+                 <div class="row footerlinks">
 

+                     <div class="col-sm-3 col-xs-6 widget">
 

+                         <h3 class="widget-title">About</h3>
 

+                         <div class="widget-body">
 

+                             <dl>
 

+                                 <dd><a href="https://fedoraproject.org/wiki/Overview">About Fedora</a></dd>
 

+                                 <dd><a href="https://getfedora.org/en/sponsors">Sponsors</a></dd>
 

+                                 <dd><a href="https://fedoramagazine.org">Fedora Magazine</a></dd>
 

+ 				<dd><a href="https://fedoraproject.org/wiki/Legal:Main#Legal">Legal</a></dd>
 

+                             </dl>
 

+                             <ul class="list-inline">
 

+                             <li>
 

+                                 <a href="https:https://www.facebook.com/TheFedoraProject" class="btn-social btn-outline"><i class="fa fa-fw fa-facebook"></i></a>
 

+                             </li>
 

+                             <li>
 

+                                 <a href="https:https://plus.google.com/112917221531140868607" class="btn-social btn-outline"><i class="fa fa-fw fa-google-plus"></i></a>
 

+                             </li>
 

+                             <li>
 

+                                 <a href="https:https://twitter.com/fedora" class="btn-social btn-outline"><i class="fa fa-fw fa-twitter"></i></a>
 

+                             </li>
 

+                         </ul>
 

+                         </div>
 

+                     </div>
 

+ 

+                     <div class="col-sm-3 col-xs-6 widget">
 

+                         <h3 class="widget-title uppercase">Download</h3>
 

+                         <div class="widget-body">
 

+                           <dl>
 

+                             <dd><a href="https://getfedora.org/en/workstation/download">Get Fedora Workstation</a></dd>
 

+                             <dd><a href="https://getfedora.org/en/server/download">Get Fedora Server</a></dd>
 

+                             <dd><a href="https://getfedora.org/en/atomic/download">Get Fedora Atomic</a></dd>
 

+                             <dd><a href="https://spins.fedoraproject.org">Fedora Spins</a></dd>
 

+                             <dd><a href="https://labs.fedoraproject.org">Fedora Labs</a></dd>
 

+                             <dd><a href="https://arm.fedoraproject.org">Fedora ARM<span class="sup">&reg;</span></a></dd>
 

+                             <dd><a href="https://alt.fedoraproject.org/">Alternative Downloads</a></dd>
 

+ 

+                         </dl>
 

+                         </div>
 

+                     </div>
 

+ 

+                     <div class="col-sm-3 col-xs-6 widget">
 

+                         <h3 class="widget-title">Support</h3>
 

+                         <div class="widget-body">
 

+                             <dl>
 

+                                 <dd><a href="https://fedoraproject.org/wiki/Communicating_and_getting_help">Get Help</a></dd>
 

+                                 <dd><a href="https://ask.fedoraproject.org/">Ask Fedora</a></dd>
 

+                                 <dd><a href="https://fedoraproject.org/wiki/Common_F27_bugs">Common Bugs</a></dd>
 

+                                 <dd><a href="https://developer.fedoraproject.org/">Fedora Developer Portal</a></dd>
 

+                                 <dd><a href="https://docs.fedoraproject.org/f27/install-guide/index.html">Installation Guide</a></dd>
 

+                             </dl>
 

+                         </div>
 

+                     </div>
 

+ 

+                     <div class="col-sm-3 col-xs-6 widget">
 

+                         <h3 class="widget-title">Join</h3>
 

+                         <div class="widget-body">
 

+                             <dl>
 

+                                 <dd><a href="https://fedoraproject.org/wiki/Join">Join Fedora</a></dd>
 

+                                 <dd><a href="http://fedoraplanet.org">Planet Fedora</a></dd>
 

+                                 <dd><a href="https://fedoraproject.org/wiki/SIGs">Fedora SIGs</a></dd>
 

+                                 <dd><a href="https://admin.fedoraproject.org/accounts/">Fedora Account System</a></dd>
 

+                                 <dd><a href="https://fedoracommunity.org/">Fedora Community</a></dd>
 

+                             </dl>
 

+                         </div>
 

+                     </div>
 

+                 </div> <!-- /row of widgets -->
 

+ 

+                 <div class="row">
 

+                     <div class="col-md-2">
 

+                         <div class="widget-body">
 

+                             <a href="https://www.redhat.com/"><img class="rh-logo" src="_images/redhat-logo.png" alt="Red Hat Logo" /></a>
 

+                         </div>
 

+                     </div>
 

+                     <div class="col-md-7">
 

+                         <div class="widget-body">
 

+                             <p class="sponsor">Fedora is sponsored by Red Hat.</p>
 

+                             <p class="sponsor"><a href="https://www.redhat.com/en/technologies/linux-platforms/articles/relationship-between-fedora-and-rhel">Learn more about the relationship between Red Hat and Fedora &raquo;</a></p>
 

+                             <p class="copy">&copy; 2017 Red Hat, Inc. and others. Please send any comments or corrections to the <a href="https://pagure.io/fedora-docs/docs-fp-o">documentation team</a></p>
 

+                         </div>
 

+                     </div>
 

+                 </div> <!-- /row of widgets -->
 

+ 

+             </div>
 

+         </div>
 

+     </div>
 

+     <!-- jQuery (necessary for Bootstrap's JavaScript plugins) -->
 

+     <script src="https://ajax.googleapis.com/ajax/libs/jquery/1.11.3/jquery.min.js"></script>
 

+     <!-- Include all compiled plugins (below), or include individual files as needed -->
 

+     <script src="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.5/js/bootstrap.min.js"></script>
 

+   </body>
 

+ </html>

This is a copy of _image/404.html. The source file should be removed
after server configuration is updated in #20.

I believe we may need to rename this file in the root directory. Can you look at http://asciibinder.org/latest/guides/maintainer_guide.html#sites-and-homepages and run a test build?

Test build gives there warnings. Is it okay?

$ asciibinder package -l debug
Building all distributions.
CHANGING TO BRANCH 'master-en-US'
WARN: Branch 'master-en-US' includes the following .adoc files that are not referenced in the _topic_map.yml file:
- Common_Content/Feedback
- Common_Content/Legal_Notice
Building Fedora for branch 'master-en-US'
CHANGING TO BRANCH 'f28-en-US'
WARN: Branch 'f28-en-US' includes the following .adoc files that are not referenced in the _topic_map.yml file:
- Common_Content/Feedback
- Common_Content/Legal_Notice
...

I also can not test build from my branch - build script resets branch to master, and there is no 404.html file at that place. Now merging 404 branch to master for testing.

And now the build fails in asciibinder package:

CHANGING TO BRANCH 'Fedora-Council_council-docs'
Error: The topic map file at '_topic_map.yml' contains the following errors:
- Topic entity at 'Fedora Subprojects -> Engineering -> Fedora Modularity -> What is Modularity' exceeds the maximum nested depth.
- Topic entity at 'Fedora Subprojects -> Engineering -> Fedora Modularity -> How does it work' exceeds the maximum nested depth.
- Topic entity at 'Fedora Subprojects -> Engineering -> Fedora Modularity -> How does it work -> Main Concepts' exceeds the maximum nested depth.

No, I can't do anything right now, because of this failing build, and I don't know what needs to be fixed about those nesting levels.

I also can not test build from my branch - build script resets branch to master, and there is no 404.html file at that place. Now merging 404 branch to master for testing.

Sorry for the delayed response. I was traveling last week.

To fix this, modify the line master: in _distro_map.yml to refer to your branch.

No, I can't do anything right now, because of this failing build, and I don't know what needs to be fixed about those nesting levels.

Use the upstream code and run

asciibinder package -t 0

To fix this, modify the line master: in _distro_map.yml to refer to your branch.

There is no master: line in that file - https://pagure.io/fedora-docs/docs-fp-o/blob/master/f/_distro_map.yml

Use the upstream code and run

asciibinder package -t 0

How to use? Current version 0.1.14 complains abou missing -t 0 option and there is no Bodhi build for a new version - https://bugzilla.redhat.com/show_bug.cgi?id=1542967

To fix this, modify the line master: in _distro_map.yml to refer to your branch.

There is no master: line in that file - https://pagure.io/fedora-docs/docs-fp-o/blob/master/f/_distro_map.yml

doh! you're right. I was thinking of tree repos. for this run the builder with the optional branch argument.

./builder my-branch
asciibinder package -t 0

Use the upstream code and run
asciibinder package -t 0

How to use? Current version 0.1.14 complains abou missing -t 0 option and there is no Bodhi build for a new version - https://bugzilla.redhat.com/show_bug.cgi?id=1542967

The latest code is upstream here: https://github.com/redhataccess/ascii_binder

Is there a way to release a new package version, at least for updates-testing? I'd like to avoid installing things on my system that I can not uninstall and that will conflict with proper packages.
Edited 6 years ago by abitrolly

Is there a way to release a new package version, at least for updates-testing? I'd like to avoid installing things on my system that I can not uninstall and that will conflict with proper packages.

This will require the upstream to cut a new release. In theory I can do that, I will look into it next week. It is lower priority for me with the antora work, however you're reasons for wanting it are the same as mine.

In the interim, I suggest you use a container.

Wrapping 0.1.15.1 is not enough? https://bugzilla.redhat.com/show_bug.cgi?id=1542967

Can not submit PR for ascii_binder because of https://pagure.io/fedora-infrastructure/issue/6361

Now I won't have more time. This is as far as I could help.

@abitrolly thank you for your help. I am closing this as we are no longer using AsciiBinder.

Pull-Request has been closed by bex
6 years ago
Metadata
None
No Tags
Changes Summary 1
+135
file added
404.html
Powered by Pagure 5.14.1
Documentation • File an Issue • About • SSH Hostkey/Fingerprint
© Red Hat, Inc. and others.