rnestertsov

HTTP Filesystem Protocol Specification

Overview

The HTTP Filesystem Protocol provides a RESTful interface for performing POSIX-like filesystem operations over HTTP. It enables hierarchical file and directory manipulation using standard HTTP methods with filesystem-specific metadata encoded in HTTP headers.

Protocol Design

Core Principles

rnestertsov

# nbg1-dc3, CX11, Ubuntu 20.04, 10 GB EXT4 Volume



# local SSD


root@voltest:~# hdparm -Tt /dev/sda
/dev/sda:
 Timing cached reads:   14624 MB in  1.99 seconds = 7341.48 MB/sec

rnestertsov

58 bytes of CSS to look great nearly everywhere

When making this website, i wanted a simple, reasonable way to make it look good on most displays. Not counting any minimization techniques, the following 58 bytes worked well for me:

main {
  max-width: 38rem;
  padding: 2rem;
  margin: auto;
}

rnestertsov

.
├── books
│   ├── handlers.go
│   └── models.go
├── config
│   └── db.go
└── main.go

rnestertsov

There are some key values that the time.Parse is looking for.

By changing:

test, err := time.Parse("10/15/1983", "10/15/1983")

to

rnestertsov

-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
--                                                                            --
--                                  mysql                                     --
--                                                                            --
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

--
-- mysql <http://sqlfiddle.com/#!9/91afb5/2>
--        note: sqlfiddle is very stupid

rnestertsov

#!/bin/sh

# Add certifiacte
sudo keytool -importcert -alias local-CA \
     -keystore "$JAVA_HOME/jre/lib/security/cacerts" \
     -file my_cert.crt

# get certificate
sudo keytool -list -keystore "$JAVA_HOME/jre/lib/security/cacerts" -alias local-CA

rnestertsov

private static void printResults(ResultSet rs) throws SQLException {
    ResultSetMetaData rsMetadata = rs.getMetaData();

    for (int i=1; i<=rsMetadata.getColumnCount(); i++) {
        System.out.printf("%-15s | ", rsMetadata.getColumnName(i));
    }
    System.out.printf("\n");

    while (rs.next()) {
        for (int i=1; i<=rsMetadata.getColumnCount(); i++) {

rnestertsov

FROM centos:7.5.1804
ARG JDK_VERSION
ARG MAVEN_VERSION
ARG NODE_VERSION

RUN yum install -y \
    wget \
    java-${JDK_VERSION}-openjdk-devel

ENV JAVA_HOME /usr/lib/jvm/java-${JDK_VERSION}-openjdk/

rnestertsov

Go has excellent build tools that mitigate the need for using make. For example, go install won't update the target unless it's older than the source files.

However, a Makefile can be convenient for wrapping Go commands with specific build targets that simplify usage on the command line. Since most of the targets are "phony", it's up to you to weigh the pros and cons of having a dependency on make versus using a shell script. For the simplicity of being able to specify targets that can be chained and can take advantage of make's chained targets,