Skip to main content

ocsigen upload two files with dynamic name

The goal

I want to upload two files, and put the IP address of the uploader in the filename

The solution

 open Lwt open XHTML.M open Eliom_services open Eliom_parameters open Eliom_sessions open Eliom_predefmod.Xhtml  let upload = Eliom_services.new_service   ~path:[""]   ~get_params:unit ();;  let upload2 = register_new_post_service   ~fallback:upload   ~post_params:((file "file_horizontal")**(file "file_vertical"))   (fun sp () (f_h,f_v) ->      let to_display =        let name_h = ("/tmp/t_f_h-"^(Unix.string_of_inet_addr (Eliom_sessions.get_remote_inet_addr sp)))         and name_v = ("/tmp/t_f_v-"^(Unix.string_of_inet_addr (Eliom_sessions.get_remote_inet_addr sp)))         in          (try  Unix.unlink name_h           with _ -> ()); (Eliom_sessions.get_tmp_filename f_h) name_h;          (try  Unix.unlink name_v           with _ -> ()); (Eliom_sessions.get_tmp_filename f_v) name_v;          (name_h^" et aussi "^name_v);      in        Lwt.return          (html             (head (title (pcdata "Upload")) [])             (body [h1 [pcdata to_display]])));;   let uploadform =    register upload     (fun sp () () ->        let f =          (post_form upload2 sp             (fun (file_horizontal, file_vertical) ->                [p [file_input ~name:file_horizontal ();                    br ();                    file_input ~name:file_vertical ();                    br ();                    string_input ~input_type:`Submit ~value:"Send" ()]]             ) ())         in          Lwt.return            (html               (head (title (pcdata "form")) [])               (body [f])));;  


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

Jira workflow for new projects

Associated workflow creation I'm a Jira Cloud user and begining from some version 6, I noticed that when I create a project, it automatically creates a Workflow and Issue Scheme that is prepended by the project key and which is a copy of the default scheme. I always had to make a cleanup after creating a project. Default workflow for new projects I also miss a feature that would allow me to make a custom workflow (and globally custom project setting) the default for new projects I create. Solution: Create with shared configuration While searching, I noticed that with Jira Cloud which is version 7.1.0 at the time I write, there is a link at the bottom of the "Create project" wizard: "Create with shared configuration" will allow me to select the project I want the new one to share configuration with. The new created project will use the same configuration as the project I select There will be no creation of Workflow and Issue Scheme that