gbalint

cd 3-5-8_perces_mesek_elalvashoz_es_osszebujashoz && cp *_300px.jpg *_1000px.jpg *_fulszoveg.docx ~/penny_belistazas && cd ..
cd 3-5-8_perces_mesek_hos_lovagokrol_es_bator_kalozlanyokrol && cp *_300px.jpg *_1000px.jpg *_fulszoveg.docx ~/penny_belistazas && cd ..
cd 3-5-8_perces_mesek_mikulasra_es_karacsonyra && cp *_300px.jpg *_1000px.jpg *_fulszoveg.docx ~/penny_belistazas && cd ..
cd 3-5-8_perces_mesek_szep_almokhoz && cp *_300px.jpg *_1000px.jpg *_fulszoveg.docx ~/penny_belistazas && cd ..
cd 3-5-8_perces_mesek_unikornisokrol_es_sarkanyokrol && cp *_300px.jpg *_1000px.jpg *_fulszoveg.docx ~/penny_belistazas && cd ..
cd 3-5-8_perces_mesek_utazashoz_es_kalandozashoz && cp *_300px.jpg *_1000px.jpg *_fulszoveg.docx ~/penny_belistazas && cd ..
cd 3-5-8_perces_mesek_viccelodeshez_es_bolondozashoz && cp *_300px.jpg *_1000px.jpg *_fulszoveg.docx ~/penny_belistazas && cd ..
cd a_kuflik_es_a_mashogyoszkop && cp *_300px.jpg *_1000px.jpg *_fulszoveg.docx ~/penny_belistazas && cd ..
cd a_kuflik_es_a_mohamanyi && cp *_3

gbalint

Principles

REST api, with versioning (tell me if we don't need versioning, but imho that makes later API changes easier).

All api endpoint urls have a version prefix (/v1).

Use HTTP codes meaningfully for errors, we can add some kind of JSON error reporting later if needed

I tried to keep everything as simple as possible.

gbalint

bzz:// urls work well in a future scenario where everyone uses swarm-enabled browsers to access content. However, this is not the case now, so we need a strategy on how would we like to handle urls, so that they work well in most situations, e.g. in normal browsers, with different gateways, etc.

Let's define some terminology to describe the different user scenarios:

Client software environment

The user's software environment to access a swarm page

• public-gateway: normal browser using public http gateway
• local-gateway: normal browser and local swarm node http interface
• browser-plugin: normal browser with plugin to rewrite urls
• it rewrites bzz:// to http:///bzz:/

gbalint

We need a few special type of requests for testing/debugging purposes on swarm:

• raw: returns the raw content at the given hash
• hash: returns the hash and not the content
• list: returns the list of all the files in the manifest under the given path
• immutable: skip ENS resolving, only accept hashes

We have different kind of possible solutions on how to differentiate the requests to implement these special request types. These potential solutions all have their pros and cons.

Possible solutions

gbalint

body='{
 "request": {
   "message": "Test build from the api",
   "branch":"master",
   "config": {
     "merge_mode": "merge",
     "matrix": {
        "include": [
          {
            "os": "linux",