Skip to main content

ocsigen css and javascript in head


I would like to have this:
 < head >   < title >a sample title< /title >       < link href="style.css" type="text/css" rel="stylesheet" / >   < script type="text/javascript" src="script.js">< / script > < / head > 
This would load one "style.css" file and one "script.js" from the HEAD tag.


Static directory in configuration

There must be a "static" directory from where we load the static files.
In the "ocsigen.conf" file:
     < host >         < site path="xxxx" >             < static dir="/home/mihamina/public_html/static/" />             < eliom module="/xxx/xxx.cmo" />         < / site >      < / host > 

The (Da Mihamina) code :-)

 open Lwt open XHTML.M open Eliom_services open Eliom_parameters open Eliom_sessions open Eliom_predefmod.Xhtml   let main_handler sp () () =     Lwt.return       (html          (head (title (pcdata "ttt")) [(css_link  (make_uri (static_dir sp) sp ["style.css"]) ());                                         (js_script (make_uri (static_dir sp) sp ["script.js"]) ())])          (body [   (div [pcdata "blabla"]) ; (div [pcdata "blabla"]) ]))   let main_service =   Eliom_predefmod.Xhtml.register_new_service     ~path: [""]     ~get_params: Eliom_parameters.unit     main_handler 


Popular posts from this blog

npm run build base-href

Using NPM to specify base-href When building an Angular application, people usually use "ng" and pass arguments to that invocation. Typically, when wanting to hard code "base-href" in "index.html", one will issue: ng build --base-href='' I used to build my angular apps through Bamboo or Jenkins and they have a "npm" plugin. I got the habit to build the application with "npm run build" before deploying it. But the development team once asked me to set the "--base-href=''" parameter. npm run build --base-href=' did not set the base href in indext.html After looking for a while, I found where it says: You need to use −− to pass arguments to npm scripts. This did the job! The command to issue is then: npm run build -- --base-href='

dockerfile multiline to file

Outputing a multiline string from Dockerfile I motsly use a Dockerfile by sourcing from a base ditribution: CentOS or Debian. But I also have a local mirror and would like to use it for packages installation. Espacially on CentOS it is about many lines to write to the /etc/yum.repos.d/CentOS-Base.repo file. Easiest way: one RUN per line The first method that comes in mind is to issue one RUN per line to write. Here you are: RUN echo "[base] " > /etc/yum.repos.d/CentOS-Base.repo RUN echo "name=CentOS-$releasever - Base " >> /etc/yum.repos.d/CentOS-Base.repo RUN echo "baseurl= " >> /etc/yum.repos.d/CentOS-Base.repo RUN echo "gpgcheck=0 &quo

Gnome VNC Grey Checkboxes

When setting up VNC server in Gnome, I get a grey screen (or a black one) and the checkboxes to "Accept clipboard from viewers", "Send clipboard to viewers", "Send primary selection to viewers". I'm setting up a VNC server on a Debian 10 machine that has Gnome environment. A zillion articles can be found on Internet, they have the same global path: Install Gnome and GDM Install TigerVNC Setup the VNC Server: password + startup Run the server Connect from the client One of them is this TeknoTut how-to I took inspiration from. The tutorial is good, but I needed to complete it with extra steps in order to make it work: If the current user has already a running Gnome session, I just get the "grey screen with the checkboxes". It is good to know that: The "grey screen" is due to the "xsetroot" command that can be seen in some howtos The checkboxes are due to the "vncconfig -iconic &" command