Forem: Zimera Corporation

Bypass Transparent DNS Proxy

Bambang Purnomosidi D. P. — Thu, 21 Jul 2022 05:48:24 +0000

Since some days ago, I can not update my Devuan box. The error is "Temporary failure in name resolution". This is strange provided that Brave Browser can access deb.devuan.org. Later, I figured out that my ISP (Indihome - https://www.indihome.co.id/) uses transparent DNS proxy and Brave Browser has Secure DNS (also known as DNS Over HTTPS) so I can access deb.devuan.org from Brave Browser, but I can not access deb.devuan.org from command line.

This is why eventhough I use 8.8.8.8 in my /etc/resolv.conf, all request to DNS server is intercepted by them and then the request will be directed to ISP for whatever they want. This is unacceptable behaviour but well, complaints won't be heard, so I choose to use DNS over https.

I search for tools and found dns-over-https. This tool uses Go (1.13 or newer) so it's not a big deal for me since I already use Go. Just clone the repo and compile and then execute doh-client (Go should be available on your system):

$ git clone https://github.com/m13253/dns-over-https
$ cd dns-over-https
$ make

I don't use systemd, So just go to doh-client and run it:

$ cd doh-client
$ ./doh-client

Change /etc/resolv.conf to use 127.0.0.1 as nameserver:

nameserver 127.0.0.1

Then I can use apt from shell like before.

Getting Started with Redis and RedisGraph

Bambang Purnomosidi D. P. — Thu, 21 Oct 2021 10:06:04 +0000

Introduction

A graph is a representation of data structure which emerge from Discrete Mathematics (more specifically, studied in Graph Theory) to represent interconnected data and solving any problems related with those interconnected data. Currently, there are two big graph implementation in software:

Triple, mainly represented by RDF with SPARQL as its query language. In TripleStore, data is represented as Subject-Predicate-Object. The database for this kind of data is usually called TripleStore. An example of TripleStore is BlazeGraph.
Property Graph, mainly represented as node and relationship in which they can have properties. The database for this kind of data is usually called Graph Database. Gremlin - by TinkerPop project and Cypher - by Neo4J are their query language (also AQL - Arango Query Language - by ArangoDB, but AQL does not only provides graph query language).

In this article, we will explain Property Graph only. Some Graph DBMS which support Property Graph natively, for example:

Some other DBMS use already available DBMS engine to handle graph data, for example:

PostgreSQL with graph extension, developed by a team at Apache Software Foundation as Apache AGE. Apache AGE uses Gremlin.
Redis module for graph - RedisGraph. RedisGraph uses Cypher for its query language.
YugabyteDB provides a detail on how to represent and manipulate graph data using YugabyteDB

Let's start with RedisGraph!

Redis Installation

If you already have Redis installed using your distro, you may use them provided that you use Redis version as required in Redis module center. If not, just use your distro specific package manager. For example, in Debian-based distro, you may use:

$ sudo apt install redis-server redis-cli redis-tools

After that, go to RedisGraph installation. If you want to use the hard way - compile Redis, use this guide below. Redis src has beed downloaded from Redis website. In this article, I use version 6.2.6 with TLS.

$ tar -xvf redis-6.2.6.tar.gz
$ cd redis-6.2.6
$ make BUILD_TLS=yes
cd src && make all
make[1]: Entering directory '/home/bpdp/master/postdoc-ugm/redis-6.2.6/src'
    CC Makefile.dep
...
...
...
    CC mt19937-64.o
    LINK redis-server
    INSTALL redis-sentinel
    CC redis-cli.o
redis-cli.c: In function ‘_serverAssert’:
redis-cli.c:485:18: warning: writing 1 byte into a region of size 0 [-Wstringop-overflow=]
  485 |     *((char*)-1) = 'x';
      |     ~~~~~~~~~~~~~^~~~~
    CC cli_common.o
    LINK redis-cli
    CC redis-benchmark.o
redis-benchmark.c: In function ‘_serverAssert’:
redis-benchmark.c:269:18: warning: writing 1 byte into a region of size 0 [-Wstringop-overflow=]
  269 |     *((char*)-1) = 'x';
      |     ~~~~~~~~~~~~~^~~~~
    LINK redis-benchmark
    INSTALL redis-check-rdb
    INSTALL redis-check-aof

Hint: It's a good idea to run 'make test' ;)

make[1]: Leaving directory '/home/bpdp/master/postdoc-ugm/redis-6.2.6/src'
$

At this point, we've already got Redis compiled, ready to serve. The results are in src/:

$ ls -la src/
total 63300
drwxr-xr-x 3 bpdp bpdp   12288 Okt 21 12:15 ./
drwxr-xr-x 7 bpdp bpdp    4096 Okt  4 17:59 ../
-rw-r--r-- 1 bpdp bpdp   89642 Okt  4 17:59 acl.c
-rw-r--r-- 1 bpdp bpdp     426 Okt 21 12:15 acl.d
-rw-r--r-- 1 bpdp bpdp  287152 Okt 21 12:15 acl.o
...
...
...
-rwxr-xr-x 1 bpdp bpdp 4877400 Okt 21 12:15 redis-benchmark*
-rw-r--r-- 1 bpdp bpdp   76300 Okt  4 17:59 redis-benchmark.c
-rw-r--r-- 1 bpdp bpdp     441 Okt 21 12:15 redis-benchmark.d
-rw-r--r-- 1 bpdp bpdp  796440 Okt 21 12:15 redis-benchmark.o
-rwxr-xr-x 1 bpdp bpdp 9310280 Okt 21 12:15 redis-check-aof*
-rw-r--r-- 1 bpdp bpdp    7243 Okt  4 17:59 redis-check-aof.c
-rw-r--r-- 1 bpdp bpdp     444 Okt 21 12:15 redis-check-aof.d
-rw-r--r-- 1 bpdp bpdp   35744 Okt 21 12:15 redis-check-aof.o
-rwxr-xr-x 1 bpdp bpdp 9310280 Okt 21 12:15 redis-check-rdb*
-rw-r--r-- 1 bpdp bpdp   14772 Okt  4 17:59 redis-check-rdb.c
-rw-r--r-- 1 bpdp bpdp     444 Okt 21 12:15 redis-check-rdb.d
-rw-r--r-- 1 bpdp bpdp   89992 Okt 21 12:15 redis-check-rdb.o
-rwxr-xr-x 1 bpdp bpdp 4678976 Okt 21 12:15 redis-cli*
-rw-r--r-- 1 bpdp bpdp  318821 Okt  4 17:59 redis-cli.c
-rw-r--r-- 1 bpdp bpdp     396 Okt 21 12:15 redis-cli.d
-rw-r--r-- 1 bpdp bpdp  877064 Okt 21 12:15 redis-cli.o
-rw-r--r-- 1 bpdp bpdp   66774 Okt  4 17:59 redismodule.h
-rwxr-xr-x 1 bpdp bpdp 9310280 Okt 21 12:15 redis-sentinel*
-rwxr-xr-x 1 bpdp bpdp 9310280 Okt 21 12:15 redis-server*
...
...
...
-rw-r--r-- 1 bpdp bpdp   21090 Okt  4 17:59 zmalloc.c
-rw-r--r-- 1 bpdp bpdp     100 Okt 21 12:15 zmalloc.d
-rw-r--r-- 1 bpdp bpdp    5215 Okt  4 17:59 zmalloc.h
-rw-r--r-- 1 bpdp bpdp   50152 Okt 21 12:15 zmalloc.o
$

Just in case, if you want to check whether everything is ok, test them using make test:

$ make test
cd src && make test
make[1]: Entering directory '/home/bpdp/master/postdoc-ugm/redis-6.2.6/src'
Cleanup: may take some time... OK
Starting test server at port 21079
[ready]: 15259
...
...
...
Testing solo test
[ok]: Active defrag
[ok]: Active defrag big keys
[ok]: Active defrag big list
[ok]: Active defrag edge case
[64/64 done]: defrag (74 seconds)

                   The End

Execution time of different units:
  0 seconds - unit/printver
  0 seconds - unit/type/incr
  1 seconds - unit/protocol
  1 seconds - unit/info
  1 seconds - unit/keyspace
  2 seconds - unit/auth
  0 seconds - unit/quit
  3 seconds - unit/type/hash
  2 seconds - unit/acl
  6 seconds - unit/type/set
  5 seconds - unit/multi
  6 seconds - unit/sort
  7 seconds - unit/type/string
  7 seconds - unit/scan
  7 seconds - unit/type/stream-cgroups
  8 seconds - unit/type/list
  13 seconds - unit/other
  15 seconds - unit/expire
  16 seconds - unit/type/list-2
  12 seconds - unit/latency-monitor
  0 seconds - integration/convert-zipmap-hash-on-load
  3 seconds - integration/logging
  21 seconds - unit/type/zset
  14 seconds - integration/aof
  17 seconds - integration/replication-2
  13 seconds - integration/rdb
  30 seconds - unit/type/list-3
  8 seconds - integration/failover
  31 seconds - unit/dump
  32 seconds - unit/type/stream
  1 seconds - unit/pubsub
  2 seconds - unit/slowlog
  27 seconds - integration/block-repl
  3 seconds - integration/redis-benchmark
  1 seconds - unit/limits
  20 seconds - integration/corrupt-dump-fuzzer
  3 seconds - unit/introspection
  16 seconds - integration/psync2-pingoff
  11 seconds - integration/redis-cli
  22 seconds - integration/corrupt-dump
  3 seconds - unit/bitfield
  6 seconds - unit/introspection-2
  2 seconds - unit/lazyfree
  4 seconds - unit/wait
  23 seconds - integration/psync2-reg
  1 seconds - unit/tls
  1 seconds - unit/oom-score-adj
  8 seconds - unit/memefficiency
  14 seconds - unit/scripting
  1 seconds - unit/shutdown
  10 seconds - unit/bitops
  1 seconds - unit/networking
  3 seconds - unit/tracking
  8 seconds - unit/pendingquerybuf
  21 seconds - unit/obuf-limits
  52 seconds - integration/replication-4
  53 seconds - integration/replication-3
  47 seconds - integration/psync2
  46 seconds - unit/hyperloglog
  54 seconds - unit/maxmemory
  54 seconds - north
  123 seconds - unit/aofrw
  165 seconds - integration/replication-psync
  227 seconds - integration/replication
  74 seconds - defrag

\o/ All tests passed without errors!

Cleanup: may take some time... OK
make[1]: Leaving directory '/home/bpdp/master/postdoc-ugm/redis-6.2.6/src'
$

Check whether you have this, shows that all tests passed:

...
...
\o/ All tests passed without errors!
...
...

Now, install Redis using this command:

$ make PREFIX=/home/bpdp/software/postdoc-ugm/redis-6.2.6/ install
cd src && make install
make[1]: Entering directory '/home/bpdp/master/postdoc-ugm/redis-6.2.6/src'

Hint: It's a good idea to run 'make test' ;)

    INSTALL redis-server
    INSTALL redis-benchmark
    INSTALL redis-cli
make[1]: Leaving directory '/home/bpdp/master/postdoc-ugm/redis-6.2.6/src'
$

Don't forget to change PREFIX to a location in your own computer and then put them inside a text file so that we may source them whenever we need to use Redis (we use Fish Shell, if you use Bash or any other shell, change accordingly):

$ cat ~/env/fish/postdoc-ugm/redis-graph 
set -x PATH $HOME/software/postdoc-ugm/redis-6.2.6/bin $PATH
$

To make background save more robust, use this (if this is not done, Redis will display warning):

$ sudo sysctl vm.overcommit_memory=1
[sudo] password for bpdp:
vm.overcommit_memory = 1
$

To check:

$ source ~/env/fish/postdoc-ugm/redis-graph
$ redis-server
4596:C 21 Oct 2021 16:34:31.976 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
4596:C 21 Oct 2021 16:34:31.976 # Redis version=6.2.6, bits=64, commit=00000000, modified=0, pid=4596, just started
4596:C 21 Oct 2021 16:34:31.976 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
4596:M 21 Oct 2021 16:34:31.976 * monotonic clock: POSIX clock_gettime
                _._                                                  
           _.-``__ ''-._                                             
      _.-``    `.  `_.  ''-._           Redis 6.2.6 (00000000/0) 64 bit
  .-`` .-```

.

  ```\/    _.,_ ''-._                                  
 (    '      ,       .-`  | `,    )     Running in standalone mode
 |`-._`-...-` __...-.``-._|'` _.-'|     Port: 6379
 |    `-._   `._    /     _.-'    |     PID: 4596
  `-._    `-._  `-./  _.-'    _.-'                                   
 |`-._`-._    `-.__.-'    _.-'_.-'|                                  
 |    `-._`-._        _.-'_.-'    |           https://redis.io       
  `-._    `-._`-.__.-'_.-'    _.-'                                   
 |`-._`-._    `-.__.-'    _.-'_.-'|                                  
 |    `-._`-._        _.-'_.-'    |                                  
  `-._    `-._`-.__.-'_.-'    _.-'                                   
      `-._    `-.__.-'    _.-'                                       
          `-._        _.-'                                           
              `-.__.-'                                               

4596:M 21 Oct 2021 16:34:31.977 # Server initialized
4596:M 21 Oct 2021 16:34:31.977 * Ready to accept connections

At that point, we are ready to use Redis server from our redis-cli:

$ redis-cli
127.0.0.1:6379> help
redis-cli 6.2.6
To get help about Redis commands type:
      "help @<group>" to get a list of commands in <group>
      "help <command>" for help on <command>
      "help <tab>" to get a list of possible help topics
      "quit" to exit

To set redis-cli preferences:
      ":set hints" enable online hints
      ":set nohints" disable online hints
Set your preferences in ~/.redisclirc
127.0.0.1:6379>

Now, we are ready with Redis Server and Client. It's time to get RedisGraph ready!

RedisGraph

RedisGraph has some deps and those dependencies are not included inside their source distribution. Therefore, we need to use Git with specific tag (as of today, v2.4.11 is the latest GA). Here's how to get the source:

$ git clone https://github.com/RedisGraph/RedisGraph -b v2.4.11 --recurse-submodules -j8
Cloning into 'RedisGraph'...
remote: Enumerating objects: 49063, done.
remote: Counting objects: 100% (2906/2906), done.
remote: Compressing objects: 100% (1082/1082), done.
remote: Total 49063 (delta 1998), reused 2448 (delta 1736), pack-reused 46157
Receiving objects: 100% (49063/49063), 39.33 MiB | 114.00 KiB/s, done.
Resolving deltas: 100% (38402/38402), done.
Submodule 'deps/RediSearch' (https://github.com/RediSearch/RediSearch.git) registered for path 'deps/RediSearch'
Submodule 'deps/googletest' (https://github.com/google/googletest.git) registered for path 'deps/googletest'
Submodule 'deps/libcypher-parser' (https://github.com/RedisGraph/libcypher-parser.git) registered for path 'deps/libcypher-parser'
Submodule 'deps/rax' (https://github.com/antirez/rax.git) registered for path 'deps/rax'
Submodule 'deps/readies' (https://github.com/RedisLabsModules/readies.git) registered for path 'deps/readies'
Submodule 'deps/xxHash' (https://github.com/Cyan4973/xxHash.git) registered for path 'deps/xxHash'
Cloning to '/home/bpdp/master/postdoc-ugm/RedisGraph/deps/RediSearch'...
remote: Enumerating objects: 34395, done.        
remote: Counting objects: 100% (1802/1802), done.        
remote: Compressing objects: 100% (1097/1097), done.        
remote: Total 34395 (delta 1150), reused 1182 (delta 696), pack-reused 32593        
Receiving objects: 100% (34395/34395), 23.62 MiB | 71.00 KiB/s, done.
Resolving deltas: 100% (25261/25261), done.
Cloning to '/home/bpdp/master/postdoc-ugm/RedisGraph/deps/rax'...
remote: Enumerating objects: 668, done.        
remote: Counting objects: 100% (25/25), done.        
remote: Compressing objects: 100% (14/14), done.        
remote: Total 668 (delta 12), reused 19 (delta 11), pack-reused 643        
Receiving objects: 100% (668/668), 236.14 KiB | 1.41 MiB/s, done.
Resolving deltas: 100% (414/414), done.
Cloning to '/home/bpdp/master/postdoc-ugm/RedisGraph/deps/readies'...
remote: Enumerating objects: 2354, done.        
remote: Counting objects: 100% (833/833), done.        
remote: Compressing objects: 100% (329/329), done.        
remote: Total 2354 (delta 608), reused 675 (delta 503), pack-reused 1521        
Receiving objects: 100% (2354/2354), 390.69 KiB | 17.00 KiB/s, done.
Resolving deltas: 100% (1577/1577), done.
Cloning to '/home/bpdp/master/postdoc-ugm/RedisGraph/deps/libcypher-parser'...
remote: Enumerating objects: 3250, done.        
remote: Counting objects: 100% (68/68), done.        
remote: Compressing objects: 100% (46/46), done.        
remote: Total 3250 (delta 42), reused 43 (delta 21), pack-reused 3182        
Receiving objects: 100% (3250/3250), 2.10 MiB | 28.00 KiB/s, done.
Resolving deltas: 100% (2488/2488), done.
Cloning to '/home/bpdp/master/postdoc-ugm/RedisGraph/deps/xxHash'...
remote: Enumerating objects: 4784, done.        
remote: Counting objects: 100% (345/345), done.        
remote: Compressing objects: 100% (188/188), done.        
remote: Total 4784 (delta 189), reused 255 (delta 143), pack-reused 4439        
Receiving objects: 100% (4784/4784), 2.54 MiB | 27.00 KiB/s, done.
Resolving deltas: 100% (2922/2922), done.
Cloning to '/home/bpdp/master/postdoc-ugm/RedisGraph/deps/googletest'...
remote: Enumerating objects: 23334, done.        
remote: Counting objects: 100% (234/234), done.        
remote: Compressing objects: 100% (142/142), done.        
remote: Total 23334 (delta 120), reused 146 (delta 81), pack-reused 23100        
Receiving objects: 100% (23334/23334), 9.49 MiB | 44.00 KiB/s, done.
Resolving deltas: 100% (17191/17191), done.
Submodule path 'deps/RediSearch': checked out '68430b3c838374478dd9ffe4e361534f572b16ff'
Submodule 'deps/googletest' (https://github.com/google/googletest.git) registered for path 'deps/RediSearch/deps/googletest'
Submodule 'deps/readies' (https://github.com/RedisLabsModules/readies.git) registered for path 'deps/RediSearch/deps/readies'
Cloning to '/home/bpdp/master/postdoc-ugm/RedisGraph/deps/RediSearch/deps/googletest'...
remote: Enumerating objects: 23334, done.        
remote: Counting objects: 100% (234/234), done.        
remote: Compressing objects: 100% (148/148), done.        
remote: Total 23334 (delta 120), reused 141 (delta 75), pack-reused 23100        
Receiving objects: 100% (23334/23334), 9.56 MiB | 1.05 MiB/s, done.
Resolving deltas: 100% (17185/17185), done.
Kloning ke '/home/bpdp/master/postdoc-ugm/RedisGraph/deps/RediSearch/deps/readies'...
remote: Enumerating objects: 2354, done.        
remote: Counting objects: 100% (833/833), done.        
remote: Compressing objects: 100% (329/329), done.        
remote: Total 2354 (delta 608), reused 675 (delta 503), pack-reused 1521        
Receiving objects: 100% (2354/2354), 390.69 KiB | 853.00 KiB/s, done.
Resolving deltas: 100% (1577/1577), done.
Submodule path 'deps/RediSearch/deps/googletest': checked out 'dea0216d0c6bc5e63cf5f6c8651cd268668032ec'
Submodule path 'deps/RediSearch/deps/readies': checked out '89be267427c7dfcfaab4064942ef0f595f6b1fa3'
Submodule path 'deps/googletest': checked out '565f1b848215b77c3732bca345fe76a0431d8b34'
Submodule path 'deps/libcypher-parser': checked out '38cdee1867b18644616292c77fe2ac1f2b179537'
Submodule path 'deps/rax': checked out 'ba4529f6c836c9ff1296cde12b8557329f5530b7'
Submodule path 'deps/readies': checked out 'd59f3ad4e9b3d763eb41df07567111dc94c6ecac'
Submodule path 'deps/xxHash': checked out '726c14000ca73886f6258a6998fb34dd567030e9'
$

Now, we have RedisGraph source code complete with its dependencies. Time to install.

Installation

To install, just do make and put redisgraph.so file as the result of RedisGraph compilation to any location that we prefer.

$ cd RedisGraph
$ make
...
...
...
    CC /home/bpdp/master/postdoc-ugm/RedisGraph/src/util/thpool/pools.o
    CC /home/bpdp/master/postdoc-ugm/RedisGraph/src/util/thpool/thpool.o
    CC /home/bpdp/master/postdoc-ugm/RedisGraph/src/util/range/numeric_range.o
    CC /home/bpdp/master/postdoc-ugm/RedisGraph/src/util/range/string_range.o
    CC /home/bpdp/master/postdoc-ugm/RedisGraph/src/util/range/unsigned_range.o
    CC /home/bpdp/master/postdoc-ugm/RedisGraph/src/util/cache/cache_array.o
    CC /home/bpdp/master/postdoc-ugm/RedisGraph/src/util/cache/cache.o
    CC redisgraph.so
objcopy --only-keep-debug redisgraph.so redisgraph.so.debug
objcopy --strip-debug redisgraph.so
objcopy --add-gnu-debuglink redisgraph.so.debug redisgraph.so
make[1]: Leaving directory '/home/bpdp/master/postdoc-ugm/RedisGraph/src'
$

Configuration

Now, put redisgraph.so file to any directory and then refer it in a configuration file:

$ pwd
/home/bpdp/software/postdoc-ugm
$ cat redis-6.2.6/redis.conf
loadmodule /home/bpdp/software/postdoc-ugm/redis/modules/redisgraph.so
$

Let's Try RedisGraph!

$ redis-server /home/bpdp/software/postdoc-ugm/redis-6.2.6/redis.conf
5946:C 21 Oct 2021 16:51:57.090 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
5946:C 21 Oct 2021 16:51:57.090 # Redis version=6.2.6, bits=64, commit=00000000, modified=0, pid=5946, just started
5946:C 21 Oct 2021 16:51:57.090 # Configuration loaded
5946:M 21 Oct 2021 16:51:57.091 * monotonic clock: POSIX clock_gettime
                _._                                                  
           _.-``__ ''-._                                             
      _.-``    `.  `_.  ''-._           Redis 6.2.6 (00000000/0) 64 bit
  .-`` .-```
{% endraw %}
.
{% raw %}
  ```\/    _.,_ ''-._                                  
 (    '      ,       .-`  | `,    )     Running in standalone mode
 |`-._`-...-` __...-.``-._|'` _.-'|     Port: 6379
 |    `-._   `._    /     _.-'    |     PID: 5946
  `-._    `-._  `-./  _.-'    _.-'                                   
 |`-._`-._    `-.__.-'    _.-'_.-'|                                  
 |    `-._`-._        _.-'_.-'    |           https://redis.io       
  `-._    `-._`-.__.-'_.-'    _.-'                                   
 |`-._`-._    `-.__.-'    _.-'_.-'|                                  
 |    `-._`-._        _.-'_.-'    |                                  
  `-._    `-._`-.__.-'_.-'    _.-'                                   
      `-._    `-.__.-'    _.-'                                       
          `-._        _.-'                                           
              `-.__.-'                                               

5946:M 21 Oct 2021 16:51:57.092 # Server initialized
5946:M 21 Oct 2021 16:51:57.094 * <graph> Starting up RedisGraph version 2.4.11.
5946:M 21 Oct 2021 16:51:57.095 * <graph> Thread pool created, using 8 threads.
5946:M 21 Oct 2021 16:51:57.095 * <graph> Maximum number of OpenMP threads set to 8
5946:M 21 Oct 2021 16:51:57.095 * Module 'graph' loaded from /home/bpdp/software/postdoc-ugm/redis/modules/redisgraph.so
5946:M 21 Oct 2021 16:51:57.095 * Ready to accept connections

Let's try some Cypher query from redis-cli (query was taken from RedisGraph example):

$ redis-cli
127.0.0.1:6379> GRAPH.QUERY MotoGP "CREATE (:Rider {name:'Valentino Rossi'})-[:rides]->(:Team {name:'Yamaha'}), (:Rider {name:'Dani Pedrosa'})-[:rides]->(:Team {name:'Honda'}), (:Rider {name:'Andrea Dovizioso'})-[:rides]->(:Team {name:'Ducati'})"
1) 1) "Labels added: 2"
   2) "Nodes created: 6"
   3) "Properties set: 6"
   4) "Relationships created: 3"
   5) "Cached execution: 0"
   6) "Query internal execution time: 61.852344 milliseconds"
127.0.0.1:6379> GRAPH.QUERY MotoGP "MATCH (r:Rider)-[:rides]->(t:Team) WHERE t.name = 'Yamaha' RETURN r.name, t.name"
1) 1) r.name
   2) t.name
2) 1) 1) Valentino Rossi
      2) Yamaha
3) 1) "Cached execution: 0"
   2) "Query internal execution time: 55.436734 milliseconds"

We are all set! When we close Redis server, the graph will persist. Happy hacking!.

Belajar Rust - 03: IDE untuk Rust

Bambang Purnomosidi D. P. — Sat, 11 Sep 2021 05:32:13 +0000

IDE (Integrated Development Environment) adalah software yang digunakan sebagai peranti pengembangan terintegrasi. IDE sangat penting dalam membangun aplikasi. Produktivitas pemrogram biasanya sangat tergantung dari kepiawaiannya menggunakan IDE. Bab ini membahas tentang IDE yang bisa digunakan untk membangun aplikasi menggunakan Rust. Ada beberapa software dasar yang akan dijelaskan dan digunakan dalam pembahasan ini, yaitu:

Pada umumnya, terkait dengan IDE, ada 2 kategori:

IDE yang memang sejak awal khusus dirancang untuk suatu bahasa pemrograman tertentu. Contoh dari IDE ini antara lain adalah IDE Borland Delphi, IntelliJ IDEA, Apache NetBeans, dan lain-lain. Software jenis ini biasanya juga memberikan fasilitas pembuatan plugins untuk bahasa pemrograman lain dengan mekanisme plugins yang khusus untuk IDE tersebut, contohnya adalah Apache NetBeans yang bisa digunakan untuk C/C++, PHP, dan lain-lain. Mekanisme ini tidak cross software, artinya mekanisme plugin untuk Apache NetBeans tidak akan bisa digunakan oleh IntelliJ IDEA.
Editor teks yang bersifat umum / generik dan memerlukan konfigurasi maupun plugin / add-on / tambahan untuk keperluan penggunaan editor teks tersebut untuk keperluan suatu bahasa pemrograman.

Kecenderungan saat ini menuju ke nomor 2, bahkan beberapa IDE (kategori nomor 1) juga menggunakan mekanisme nomor 2. Mekanisme pertama memang cenderung ditinggalkan karena setiap IDE / editor teks harus secara spesifik mendefinisikan dan mengelola plugins sendiri-sendiri. Selain mendatangkan kerepotan pengelole IDE / editor teks, hal ini juga mendatangkan kerepotan komunikas serta pengembangan kompilator / interpreter bahasa pemrograman. Karena berbagai kerepotan itu, makan muncul Language Server Protocol / LSP.

Dengan menggunakan mekanisme LSP, maka setiap IDE / editor teks hanya perlu membuat dan mengelola klien LSP saja sesuai dengan protokol LSP. Setelah itu, komunitas bahasa pemrograman tertentu akan membuat dan mengelola server LSP sesuai spesifikasi protokol LSP. Dengan demikian, selama IDE / editor teks mengikuti protokol klien LSP dan tersedia server LSP dari komunitas pengembangan bahasa pemrograman, maka sudah cukup untuk menjadikan IDE / editor teks tersebut sebagai IDE bahasa pemrograman sesuai dengan server LSP yang dikembangkan komunitas pengembang bahasa pemrograman tersebut. Protokol LSP menyediakan:

Completion
Hover/tooltips
Go to definition
Show/go to references
Show method signatures
Rename
Code actions, misalnya untuk automatic formatting, organize imports,dan lain-lain.

Mekanisme LSP kurang lebih sebagai berikut:

Menjalankan IDE / Editor teks => menjalankan plugin / add-on klien LSP => mengaktifkan server LSP sesuai konfigurasi => IDE bahasa pemrograman.

Untuk kompilator Rust, server LSP dikembangkan di repo rls. Untuk menggunakan LSP, install terlebih dahulu rls:

$ rustup component add rls rust-analysis rust-src
info: downloading component 'rls'
info: installing component 'rls'
info: downloading component 'rust-analysis'
  2.8 MiB /   2.8 MiB (100 %) 868.9 KiB/s in  4s ETA:  0s
info: installing component 'rust-analysis'
info: downloading component 'rust-src'
  2.3 MiB /   2.3 MiB (100 %)   1.2 MiB/s in  2s ETA:  0s
info: installing component 'rust-src'
$

Hasilnya adalah sebagai berikut:

$ rls --version
rls 1.41.0 (a82a052 2021-07-21)
$ rls --help

    --version or -V to print the version and commit info
    --help or -h for this message
    --cli starts the RLS in command line mode
    No input starts the RLS as a language server
$

Setelah itu, IDE / editor teks dikonfigurasi untuk mengaktifkan LSP.

Vim / Neovim

Mengkonfigurasi Vim / Neovim dari awal cukup menyita waktu dan cenderung ribet. Untuk menyingkat, akan digunakan SpaceVim. Dengan menggunakan SpaceVim, kerumitan-kerumitan instalasi klien LSP akan diabstraksi oleh Spacevim, sehingga menggunakan fasilitas LSP akan lebih mudah.

Instalasi Vim

Distribusi Linux biasanya secara default sudah menginstall Vim. Jika belum, maka bisa menggunakan package manager (apt, urpmi, dnf, pacman, dan lain-lain) ataupun install dari kode sumber Vim secara langsung. Untuk OS lain, bisa mengikuti petunjuk di halaman download Vim.

Instalasi Neovim

Neovim biasanya juga tersedia di berbagai distribusi Linux dan bisa diinstall menggunakan package manager. Untuk OS lain, bisa mengikuti petunjuk di GitHub Releases page untuk Neovim.

Instalasi SpaceVim

Instalasi Spacevim dijelaskan di [URL instalasi SpaceVim]. Jika menggunakan Windows, tersedia file install.cmd yang bisa dijalankan secara langsung. Jika menggunakan Linux:

Instalasi SpaceVim untuk Vim dan Neovim

$ curl -sLf https://spacevim.org/install.sh | bash

Instalasi SpaceVim untuk Vim

$ curl -sLf https://spacevim.org/install.sh | bash -s -- --install vim

Instalasi SpaceVim untuk Neovim

$ curl -sLf https://spacevim.org/install.sh | bash -s -- --install neovim
$

Catatan: saat menginstall SpaceVim di Linux, kompilasi harus dilakukan untuk vimproc.vim. Masuk ke direktori $HOME/.SpaceVim/bundle/vimproc.vim, setelah itu berikan perintah make. Hasilnya adalah file $HOME/.SpaceVim/bundle/vimproc.vim/lib/vimproc_linux64.so*

Konfigurasi SpaceVim

Konfigurasi SpaceVim diletakkan pada file $HOME/Spacevim.d/init.toml. Berikut ini tambahan yang diperlukan untuk konfigurasi SpaceVim - Rust:

...
...
...
[[layers]]
  name = "lang#toml"

[[layers]]
  name = "lang#rust"

[[layers]]
  name = "lsp"
  filetypes = [
    "rust"
  ]
  [layers.override_cmd]
    rust = ["rls"]
...
...
...

Catatan: plugin untuk TOML juga harus diaktifkan karena konfigurasi cargo menggunakan format serialisasi TOML.

Saat menjalankan Rust, akan diinstall paket-paket yang diperlukan secara otomatis. Setelah selesai instalasi, Vim / Neovim bisa digunakan untuk IDE Rust.

Visual Studio Code / VSCodium

Visual Studio Code (selanjutnya disebut VS Code adalah IDE generik yang dibuat oleh Microsoft. VS Code dirancang untuk memungkinkan adanya penambahan fasilitas melalui Extension. Daftar lengkap extensions bisa dilihat pada Extensions Marketplace.

VSCodium adalah versi VS Code tanpa telemetry. Telemetry adalah fasilitas dari VS Code yang mengumpulkan data dari pengguna untuk keperluan layanan yang lebih baik (setidaknya, definisinya mengatakan demikian). VS Code secara default mengaktifkan fasilitas telemetry. Bagian lainnya sama dengan VS Code sehingga pembahasan tetang VS Code juga berlaku untuk VSCodium. Selanjutnya, keduanya akan disebut dengan VS Code saja.

Instalasi VS Code / VSCodium

Untuk instalasi VS Code, cukup download dari download VS Code / (download VSCodium) dan kemudian ekstraksi hasil download tersebut. Untuk menjalankan VS Code, cukup jalankan code yang terdapat pada direktori hasil ekstraksi. Jika menggunakan VSCodium, jalankan codium yang terdapat pada direktori hasil ekstraksi.

Extension untuk Rust

Extension untuk Rust di VS Code tersedia di marketplace - Rust. Untuk melakukan instalasi, tekan Ctl-P (Quick Open) dan masukkan perintah untuk instalasi berikut ini: ext install rust-lang.rust. Setelah itu, extension akan di-install:

Setelah itu, kita bisa menggunakan VS Code sebagai IDE Rust. Gunakan File - Open Folder untuk membuka proyek Rust.

Eclipse

Eclipse Foundation juga mempunyai proyek yang didedikasikan untuk membuat IDE Rust dengan basis IDE Eclipse untuk membangun aplikasi menggunakan Rust. Untuk memperoleh software ini, silahkan akses ke Web dari proyek Eclipse Corrosion. Sebagai informasi, sampai saat artikel ini ditulis, Eclipse Corrosion masih berstatus Eclipse Incubation, artinya belum menjadi proyek utama, masih masa inkubasi. Hal ini perlu diperjelas supaya memahami dukungan dari Eclipse Foundation terhadap IDE berbasis Eclipse ini.

Untuk menggunakan Eclipse Corrosion, lihat terlebih dahulu versi terbaru dari Eclipse Corrosion di https://projects.eclipse.org/projects/tools.corrosion. Setelah itu, download Eclipse Corrosion dari https://download.eclipse.org/corrosion/releases/latest/products/. Kelak, jika sudah tidak berada di posisi inkubasi, Eclipse Corrosion akan bisa diambil dari download utama Eclipse.

Catatan: untuk menggunakan Eclipse, setidaknya harus memiliki JRE (Java Runtime Environment) versi 8.

Setelah itu, ekstrak hasil download:

$ tar -xvf eclipseide-rust-1.2.1-linux.gtk.x86_64.tar.gz 
eclipse/
eclipse/p2/
eclipse/p2/org.eclipse.equinox.p2.engine/
eclipse/p2/org.eclipse.equinox.p2.engine/profileRegistry/
eclipse/p2/org.eclipse.equinox.p2.engine/profileRegistry/CorrosionIDE.profile/
eclipse/p2/org.eclipse.equinox.p2.engine/profileRegistry/CorrosionIDE.profile/1623857155371.profile.gz
eclipse/p2/org.eclipse.equinox.p2.engine/profileRegistry/CorrosionIDE.profile/.lock
eclipse/p2/org.eclipse.equinox.p2.engine/profileRegistry/CorrosionIDE.profile/.data/
eclipse/p2/org.eclipse.equinox.p2.engine/profileRegistry/CorrosionIDE.profile/.data/org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions/
eclipse/p2/org.eclipse.equinox.p2.engine/profileRegistry/CorrosionIDE.profile/.data/org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions/jvmargs
eclipse/p2/org.eclipse.equinox.p2.engine/profileRegistry/CorrosionIDE.profile/.data/.settings/
eclipse/p2/org.eclipse.equinox.p2.engine/profileRegistry/CorrosionIDE.profile/.data/.settings/org.eclipse.equinox.p2.artifact.repository.prefs
eclipse/p2/org.eclipse.equinox.p2.engine/profileRegistry/CorrosionIDE.profile/.data/.settings/org.eclipse.equinox.p2.metadata.repository.prefs
eclipse/p2/org.eclipse.equinox.p2.engine/profileRegistry/CorrosionIDE.profile/1623857155392.profile.gz
...
...
...
eclipse/plugins/org.eclipse.corrosion_1.2.1.202106081156.jar
eclipse/icon.xpm
eclipse/eclipse
eclipse/.eclipseproduct
eclipse/readme/
eclipse/readme/readme_eclipse.html
eclipse/dropins/
eclipse/eclipse.ini
eclipse/configuration/
eclipse/configuration/org.eclipse.equinox.simpleconfigurator/
eclipse/configuration/org.eclipse.equinox.simpleconfigurator/bundles.info
eclipse/configuration/config.ini
eclipse/configuration/org.eclipse.update/
eclipse/configuration/org.eclipse.update/platform.xml
$

Hasil ekstrak adalah direktori eclipse dengan isi sebagai berikut:

$ cd eclipse/
$ ls -la
total 376
drwxr-xr-x  8 zaky zaky   4096 Jun 16 22:25 ./
drwxr-xr-x  4 zaky zaky   4096 Sep 11 11:40 ../
-rw-r--r--  1 zaky zaky  84784 Jun 16 22:25 artifacts.xml
drwxr-xr-x  4 zaky zaky   4096 Jun 16 22:25 configuration/
drwxr-xr-x  2 zaky zaky   4096 Jun 16 22:25 dropins/
-rwxr-xr-x  1 zaky zaky  80072 Jun 12 04:14 eclipse*
-rw-r--r--  1 zaky zaky    821 Jun 16 22:25 eclipse.ini
-rw-r--r--  1 zaky zaky     61 Jun 12 03:06 .eclipseproduct
drwxr-xr-x 37 zaky zaky   4096 Jun 16 22:25 features/
-rwxr-xr-x  1 zaky zaky 140566 Jun 12 04:14 icon.xpm*
drwxr-xr-x  4 zaky zaky   4096 Jun 16 22:25 p2/
drwxr-xr-x 11 zaky zaky  32768 Jun 16 22:25 plugins/
drwxr-xr-x  2 zaky zaky   4096 Jun 16 22:25 readme/
$

Untuk menjalankan Eclipse for Rust Developers, masuk ke direktori hasil ekstrak kemudian eksekusi
file eclipse sebagai berikut:

$ cd eclipse
$ ./eclipse

Setelah splash screen, Eclipse akan menanyakan workspace tempat menyimpan berbagai proyek Rust. Isikan seperti yang anda kehendaki (bebas), setelah itu,
klik pada Launch, maka akan dimunculkan window utama dari Eclipse. Sebelum mulai menggunakan Eclipse for Rust, isikan Rust Preferences dengan memilih Window - Rust Preferences:

Setelah isian sesuai, kita bisa menggunakan Eclipse for Rust:

Managing a Software Development Team: Some Experiences

Bambang Purnomosidi D. P. — Mon, 06 Sep 2021 04:34:21 +0000

Introduction

Managing a software development team is never an easy task. It consists of 2 sides:

technical things
non-technical things.

This task is often assigned to the project manager, VP Engineering, Software Development Manager, etc. To be succeed, one has to consider those 2 sides. In this article, I will ouline some of my experiences in managing a software development team. This list is not meant to be complete nor perfect. You may need more but at least you will be in the safety line level one if you do care with these issues.

Decide the tools which will be used by the team

Well, this is a bad news if you don’t have enough technical capabilities. Once you don’t decide the tools, your team will be confuse as they have more than one preferences. It’s not funny to have your team uses PHP with different versions, some use WAMP while the others use XAMPP or maybe PHP which comes from some Linux distros. It’s not funny to have your team uses Notepad, Visual Studio Code, Textpad, Vim, Netbeans, Eclipse, for their IDE/Text Editor. This will waste much time and bandwidth. Consider this, if they use different tools, then when someone says: “uh oh, my Vim always give me a tab and not some spaces, how do I turn the tab into spaces?” and then nobody can answer this and probably think “that is your responsibility, I don’t care because I never use Vim”. Now consider if everybody uses Netbeans (note: I don’t have any relation whatsoever with Netbeans nor a Netbeans evangelist), when someone yell “How do I create a new PHP module in Netbeans?”, chances are some of the guys in your team know about this.

Use a specific software development methodology, probably with some minor adaption

A software development methodology consists of process and modelling. It guides the team through the process and enable the team to model the software which is built by the team to solve client problems. It is important to use the specific methodology so that everyone in the team knows what and how to do the development. If you don’t decide any methodology, then your team won’t have any guides. Remember, you have to use a specific methodology but don’t be too rigid. Your team may consists of people from many backgounds with many level of capabilities. For example, you may use a Unified Process methodology but because your team is limited and don’t have time to learn how to use UML, then don’t push them to use rigid UP methodology. The most important thing here is process. Do use that process but don’t be too rigid.

Make some conventions regarding technical issues

Again, this is important to keep the team away from the state of flux and let the guys in the team communicate with the same language. You surely don’t want your team to have more than one variable / property naming system, right? What if some programmers use “this_is_a_variable”, while the others use “thisIsAVariable”? quite confusing, I guess. You may need to define some coding conventions and probably uses software tool to force this conventions, for example if your team uses Rust, clippy can help you and your team.

Enforce Programming Idiom

Every programming language, together with their ecosystems and development tools are such a complex beast. Usually, in the beginning, the most important thing is "it works!", but turns out that this may decrease productivity since there are more than one thing to do somenthing, reducing readability. Enforcing programming idiom is important to increase source code readability.

Know the client(s) and their problems which are tried to be solved

You must understand this good enough so that you can define the scope of the problems and deal with the problems.

Decide the scope of the problems and insists on this.

Clients basically don’t understand the requirements, so your duty as a leader is to define the scope of the problems which are tried to be solved by the software. You must cooperate nicely with the client and have the information understood by all team members. From programmers’ point of view, the uncertainty caused by scope uncertainty will lead to frustration. Well, I do understand that agile methodologies encourage changes, but who want to deal with changes everytime? What I am trying to say is, a software development leader should understand that changes are possible but this should be done within the scope. Don’t play with programmers’ heart 😉

Have a good interpersonal relationship and don’t be a jerk

I know that this software development task is not easy. Clients always ask the progress and the team is in a stress condition. It really helps to just stay with the team and always willing to help them whatever you can than just act like a jerk who walks here and there and yelling. Trust me, the team will respect you more if you are always willing to help them.

Never let the team in a state of flux

Uncertainty comes everytime. Whenever the team has anything uncertain, your decision is needed to keep them away from confusion. You do understand that you have to have a good grasp in technical side and problem domain to make a good decision, don’t you?

Let the team concentrate on technical matters

Ok, pay attention more to non technical matters so that the team can concentrate on technical side. Don’t let them do any clerical things since programmers (usually) hate to do administrative things. It’s good to have a dedicated person to deal with all administrative things.

Let the team member knows each other about progress and difficulties

Opennes is important. By let them know each other’s progress, you keep them in a fair situation. Low salary probably can be understood, but unfair treatment can not be tolerated.

Inform the team about your progress too

So you think you can hide your progress? The team will surely want to know that you do your jobs too. If you hide your progress, they will lose respect and trust in you.

Communicate. Communicate. Communicate

I can not emphasize this more. This is really important for the team to have them communicate each other. Your tasks will be to communicate with them and act as a liaison between the team and the client. Oh and don’t forget, have a good sense of humour.

Always keep backup of everything

You don’t need to backup everything if you are sure that you always live in an ideal situation. You should keep backup in more than one place. Compress them and have them uploaded anywhere on the Internet or in a storage server if possible.

Use Version Control System

Version control system is a software which can be used to track the software source code versioning. You may use Git or Mercurial for this purpose. With version control systems, the progress is transparant. Also, any bugs and improvement can be tracked.

Use web based bug tracking system, project management software, and/or wiki

This will keep any information handy and on track. All any other members can also see the project’s progress. It will keep each team members informed and any unfair situation can be detected. Usually, they are now available in GitHub or GitLab.

Belajar Rust - 02: Instalasi Rust

Bambang Purnomosidi D. P. — Sat, 04 Sep 2021 10:37:09 +0000

Untuk menggunakan Rust, tentu saja anda harus melakukan instalasi terhadap Rust dan ekosistem yang bisa digunakan untuk mendukung proses membangun software menggunakan Rust. Bagian ini membahas tentang berbagai cara yang bisa digunakan untuk mulai menggunakan Rust. Selain itu, di bab ini juga akan dibahas tentang berbagai peranti pengembangan yang lazim digunakan sebagai hasil dari instalasi serta pengenalan penggunaannya.

Rilis Rust

Rust mempunyai 3 kategori rilis:

Stable: rilis stabil, dengan test yang dilakukan secara menyeluruh.
Beta: rilis versi ini merupakan rilis yang disiapkan untuk menjadi versi stabil berikutnya.
Nightly: rilis versi ini merupakan rilis yang berisi berbagai eksperimen yang mungkin bisa masuk ke versi stabil berikutnya (setelah melalui versi Beta). Meskipun demikian, bisa juga eksperimen-eksperimen tersebut tidak akan pernah dimasukkan ke rilis resmi Rust.

Saat membangun aplikasi, pemrogram bebas untuk menggunakan kategori rilis manapun. Meskipun demikian, dianjurkan untuk menggunakan versi Stable karena fitur yang ada di dalamnya adalah fitur-fitur yang sudah stabil sehingga memudahkan pemrogram untuk me-maintain aplikasi yang dikembangkan.

Untuk semua rilis tersebut, Rust menggunakan pedoman yang disebut dengan Semantic Versioning. Dengan menggunakan pedoman ini, setiap penomoran rilis Rust terdiri atas 3 bagian:

MAJOR: rilis dengan perubahan API (Application Programming Intergace) yang tidak kompatibel dengan versi MAJOR sebelumnya.
MINOR: rilis dengan penambahan fungsionalitas yang kompatibel dengan versi sebelumnya.
PATCH: rilis dengan perbaikan terhadap bugs yang kompatibel dengan versi MAJOR dan MINOR.

Sebagai contoh, versi 1.54.0 dari versi Rust berisi Rust dengan semua API yang kompatibel dengan versi 1.x.x sebelumnya. Angka 54 berarti penambahan fungsionalitas yang bersifat kompatibel dengan versi penambahan fungsionalitas sebelumnya. Angka 0 berarti sama sekali belum ada perubahan perbaikan bug (jika ada) untuk versi 1.54 tersebut.

Siklus Rilis Rust

Versi dari Rust (stable, beta, nightly) dirilis setiap 6 minggu sekali (1.5 bulan sekali). Jadi, setiap 6 minggu akan muncul versi stable, beta, serta nightly). Kepastian siklus rilis ini menarik dan memberi kepastian kepada para pemrogram dalam mengantisipasi versi yang akan digunakan.

Edisi Rust

Selain versi Rust berdasarkan semantic versioning seperti yang telah dijelaskan di atas, Rust juga mengenal istilah Rust Edition / Edisi Rust. Edisi Rust menggunakan tahun dan digunakan untuk memecahkan masalah backward compatibility antara berbagai versi semantik.

Saat versi stabil pertama Rust dirilis (1.x.x), Rust mempunyai janji backward compatibility, artinya kode sumber yang dibuat untuk versi 1.x.x awal dulu, sampai versi 1.x.x terakhir tetap bisa dikompilasi dan dijalankan menggunakan Rust versi 1.x.x terakhir. Jadi, selama masih berada di versi MAJOR yang sama, maka hal tersebut kompatibel. Problem dari hal ini adalah jika ingin merilis versi semantik Rust 1.x.x yang memungkinkan terjadinya breaking changes (perubahan yang "merusak" - membuat tidak bisa dikompilasi). Sebagai contoh, Rust versi 1.x.x terakhir memperkenalkan kata kunci yang belum ada di versi awal-awal dulu. Jika dikompilasi dengan versi semantik Rust terakhir, maka akan terjadi error. Untuk itu, maka dibuat versi edisi Rust. Setiap edisi Rust akan menjamin backward compatibility terkecuali jika pemrogram dengan sadar telah melakukan berbagai perubahan yang diperlukan dan memilih edisi Rust versi berikutnya. Jika tidak mau dan ingin tetap bisa dikompilasi, maka pemrogram tetap bisa memilih untuk berada pada edisi Rust yang sebelumnya.

Sampai saat ini, ada beberapa edisi Rust:

Rust 2015: fokus pada kestabilan.
Rust 2018: fokus pada produktivitas.
Rust 2021: belum dirilis sampai saat ini.

Saat membuat suatu proyek kode sumber baru, secara default akan digunakan versi edisi Rust yang aktif saat ini.

Rust Playground

Jika kebutuhan kita hanya untuk mencoba beberapa bagian kode sumber, maka kita cukup hanya menggunakan Rust Playground saja. Setelah mengakses URL tersebut, kita bisa menuliskan kode sumber dan menjalankan kode sumber tersebut tanpa perlu melakukan instalasi peranti pengembangan Rust.

Instalasi Rust

Instalasi Rust bisa dilakukan dengan berbagai macam cara, tetapi cara yang paling mudah dan dianjurkan adalah dengan menggunakan rustup. Prasyarat software yang diperlukan adalah curl yang biasanya sudah terinstall di sistem Linux.

$ curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
info: downloading installer

Welcome to Rust!

This will download and install the official compiler for the Rust
programming language, and its package manager, Cargo.

Rustup metadata and toolchains will be installed into the Rustup
home directory, located at:

  /home/zaky/.rustup

This can be modified with the RUSTUP_HOME environment variable.

The Cargo home directory located at:

  /home/zaky/.cargo

This can be modified with the CARGO_HOME environment variable.

The cargo, rustc, rustup and other commands will be added to
Cargo's bin directory, located at:

  /home/zaky/.cargo/bin

This path will then be added to your PATH environment variable by
modifying the profile files located at:

  /home/zaky/.profile
  /home/zaky/.bashrc

You can uninstall at any time with rustup self uninstall and
these changes will be reverted.

Current installation options:


   default host triple: x86_64-unknown-linux-gnu
     default toolchain: stable (default)
               profile: default
  modify PATH variable: yes

1) Proceed with installation (default)
2) Customize installation
3) Cancel installation
>1

info: profile set to 'default'
info: default host triple is x86_64-unknown-linux-gnu
info: syncing channel updates for 'stable-x86_64-unknown-linux-gnu'
info: latest update on 2021-07-29, rust version 1.54.0 (a178d0322 2021-07-26)
info: downloading component 'cargo'
  6.0 MiB /   6.0 MiB (100 %)   1.2 MiB/s in  5s ETA:  0s
info: downloading component 'clippy'
  2.4 MiB /   2.4 MiB (100 %)   1.2 MiB/s in  2s ETA:  0s
info: downloading component 'rust-docs'
 16.7 MiB /  16.7 MiB (100 %)   1.2 MiB/s in 14s ETA:  0s
info: downloading component 'rust-std'
 21.9 MiB /  21.9 MiB (100 %)   1.2 MiB/s in 19s ETA:  0s
info: downloading component 'rustc'
 50.1 MiB /  50.1 MiB (100 %)   1.2 MiB/s in 44s ETA:  0s 
info: downloading component 'rustfmt'
  3.7 MiB /   3.7 MiB (100 %)   1.2 MiB/s in  3s ETA:  0s
info: installing component 'cargo'
info: installing component 'clippy'
info: installing component 'rust-docs'
 16.7 MiB /  16.7 MiB (100 %)   9.1 MiB/s in  1s ETA:  0s
info: installing component 'rust-std'
 21.9 MiB /  21.9 MiB (100 %)  12.5 MiB/s in  2s ETA:  0s
info: installing component 'rustc'
 50.1 MiB /  50.1 MiB (100 %)  13.7 MiB/s in  4s ETA:  0s
info: installing component 'rustfmt'
info: default toolchain set to 'stable-x86_64-unknown-linux-gnu'

  stable-x86_64-unknown-linux-gnu installed - rustc 1.54.0 (a178d0322 2021-07-26)


Rust is installed now. Great!

To get started you may need to restart your current shell.
This would reload your PATH environment variable to include
Cargo's bin directory ($HOME/.cargo/bin).

To configure your current shell, run:
source $HOME/.cargo/env
$

Setelah proses instalasi tersebut, ada file berisi variabel lingkungan (environment variables) yang harus diaktifkan, yaitu $HOME/.cargo/env. Berikut adalah kondisi sebelum diaktifkan dan setelah diaktifkan menggunakan perintah source:

$ rustc
-bash: rustc: perintah tidak ditemukan
$ cargo
-bash: cargo: perintah tidak ditemukan
$ source .cargo/env
$ rustc --version
rustc 1.54.0 (a178d0322 2021-07-26)
$ cargo --version
cargo 1.54.0 (5ae8d74b3 2021-06-22)
$

Secara default, isi dari file .cargo/env sudah diletakkan pada file .profile sehingga akan aktif setiap login. Setelah instalasi, silahkan logout dari shell dan kemudian mengaktifkan shell kembali supaya .profile dieksekusi oleh shell. Periksa hasil instalasi berikut ini:

$ rustc --version
rustc 1.54.0 (a178d0322 2021-07-26)
$ cargo --version
cargo 1.54.0 (5ae8d74b3 2021-06-22)
$ rustfmt --version
rustfmt 1.4.37-stable (a178d03 2021-07-26)
$

Untuk mencoba kompilator / compiler Rust, buat file hello.rs di lokasi direktori bebas:

fn main() {

    println!("Hello World!");

}

Untuk mengkompilasi dan menjalankan hasil:

$ rustc hello.rs 
$ ls -la
total 3216
drwxr-xr-x 2 zaky zaky    4096 Sep  4 11:58 ./
drwxr-xr-x 6 zaky zaky    4096 Sep  4 11:57 ../
-rwxr-xr-x 1 zaky zaky 3280808 Sep  4 11:58 hello*
-rw-r--r-- 1 zaky zaky      46 Sep  4 11:58 hello.rs
$ ./hello 
Hello World!
$

Catatan: rustc adalah kompilator Rust, sedangkan hello.rs adalah file kode sumber yang akan dikompilasi menjadi native machine code (lihat hasil file hello) di atas.

Proses kompilasi tersebut merupakan proses kompilasi yang digunakan secara sederhana, cukup untuk 1 file kode sumber saja. Jika software mulai kompleks dan memerlukan banyak kode sumber serta mempunyai ketergantungan / dependecy ke berbagai pustaka, maka diperlukan cargo.

Uninstall Rust

Untuk menghapus instalasi Rust, gunakan rustup yang sudah terinstall saat melakukan instalasi Rust. Berikut ini adalah cara menghapus instalasi Rust:

$ rustup self uninstall


Thanks for hacking in Rust!

This will uninstall all Rust toolchains and data, and remove
$HOME/.cargo/bin from your PATH environment variable.

Continue? (y/N) y

info: removing rustup home
info: removing cargo home
info: removing rustup binaries
info: rustup is uninstalled
$

Memperbarui Rust

Jika muncul versi terbaru dari Rust, maka kita bisa memperbarui Rust hanya dengan menggunakan rust update berikut ini:

$ rustup update
info: syncing channel updates for 'stable-x86_64-unknown-linux-gnu'
679.5 KiB / 679.5 KiB (100 %) 623.0 KiB/s in  1s ETA:  0s
info: latest update on 2021-09-09, rust version 1.55.0 (c8dfcfe04 2021-09-06)
info: downloading component 'cargo'
  6.1 MiB /   6.1 MiB (100 %) 981.4 KiB/s in  6s ETA:  0s
info: downloading component 'clippy'
  2.4 MiB /   2.4 MiB (100 %)   1.1 MiB/s in  2s ETA:  0s
info: downloading component 'rust-docs'
 17.0 MiB /  17.0 MiB (100 %)   1.2 MiB/s in 15s ETA:  0s
info: downloading component 'rust-std'
 22.3 MiB /  22.3 MiB (100 %) 780.8 KiB/s in 23s ETA:  0s 
info: downloading component 'rustc'
 51.0 MiB /  51.0 MiB (100 %)   1.1 MiB/s in 52s ETA:  0s 
info: downloading component 'rustfmt'
  3.7 MiB /   3.7 MiB (100 %) 943.6 KiB/s in  4s ETA:  0s
info: removing previous version of component 'cargo'
info: removing previous version of component 'clippy'
info: removing previous version of component 'rust-docs'
info: removing previous version of component 'rust-std'
info: removing previous version of component 'rustc'
info: removing previous version of component 'rustfmt'
info: installing component 'cargo'
info: installing component 'clippy'
info: installing component 'rust-docs'
 17.0 MiB /  17.0 MiB (100 %)   7.7 MiB/s in  2s ETA:  0s
info: installing component 'rust-std'
 22.3 MiB /  22.3 MiB (100 %)  12.3 MiB/s in  2s ETA:  0s
info: installing component 'rustc'
 51.0 MiB /  51.0 MiB (100 %)  10.2 MiB/s in  6s ETA:  0s
info: installing component 'rustfmt'
info: checking for self-updates

  stable-x86_64-unknown-linux-gnu updated - rustc 1.55.0 (c8dfcfe04 2021-09-06) (from rustc 1.54.0 (a178d0322 2021-07-26))

info: cleaning up downloads & tmp directories
$

Plugin untuk subcommand `Cargo`

Cargo memungkinkan untuk diperluas fungsionalitasnya dengan menggunakan plugin. Dengan menggunakan plugin, Cargo akan mendapatkan subcommand. Sebagai contoh, pada bagian ini akan dijelaskan tentang salah satu plugin yang bermanfaat untuk mendeteksi paket yang perlu diperbarui di skala user (bukan per proyek). Plugin tersebut adalah plugin cargo-update.

Instalasi Plugin

Instalasi dilakukan dengan menggunakan cargo install:

$ cargo install cargo-update
    Updating crates.io index
  Downloaded cargo-update v7.0.1
  Downloaded 1 crate (44.4 KB) in 1.45s
  Installing cargo-update v7.0.1
  Downloaded dirs-sys v0.3.6
...
...
...
   Compiling semver v0.9.0
   Compiling cargo-update v7.0.1
   Compiling url v2.2.2
   Compiling git2 v0.11.0
    Finished release [optimized] target(s) in 1m 24s
  Installing /home/zaky/.cargo/bin/cargo-install-update
  Installing /home/zaky/.cargo/bin/cargo-install-update-config
   Installed package `cargo-update v7.0.1` (executables `cargo-install-update`, `cargo-install-update-config`)
$

Untuk memeriksa pembaruan:

$ cargo install-update -a
    Updating registry 'https://github.com/rust-lang/crates.io-index'

Package       Installed  Latest  Needs update
cargo-update  v7.0.1     v7.0.1  No

No packages need updating.
Overall updated 0 packages.

Memahami Ekosistem Rust

Mempelajari suatu bahasa pemrograman tidak hanya cukup dengan mempelajari sintaksis saja. Setiap bahasa pemrograman biasa mempunyai spesifikasi, kompilator/interpreter, pengelola paket pustaka, IDE, komunitas, dan lain-lain. Pemahaman mengenai ekosistem saat mempelajari suatu bahasa pemrograman menjadi hal yang sangat penting. Biasanya pemrogram mudah mempelajari sintaksis tetapi cukup perlu waktu lama untuk memahami ekosistem. Ekosistem ini juga menentukan bagaimana seorang pemrogram bisa produktif serta menggunakan idiom-idiom yang sesuai dengan bahasa pemrograman yang ditekuni. Pada bagian ini, kita akan mempelajari ekosistem dari bahasa pemrograman Rust.

Pustaka Rust

Pustaka / library Rust sering disebut dengan istilah crate. Crate dari komunitas dipusatkan di https://crates.io/. Pengelolaan pustaka dalam suatu proyek software yang dikembangkan menggunakan Rust dilakukan oleh cargo.

Pengenalan Cargo

cargo adalah bagian dari peranti pengembangan Rust yang digunakan untuk mengelola paket-paket pustaka yang digunakan dalam suatu proyek. Selain itu, cargo juga bisa digunakan untuk keperluan menangani berbagai proses yang diperlukan oleh proyek, misalnya membangun (build), test, menjalankan run, dan masih banyak lagi. Selain fasilitas resmi, cargo juga menyediakan plugins untuk menambahkan kemampuan dari cargo. Daftar plugins bisa diperoleh dengan mengakses https://crates.io/search?q=cargo.

Inisialisasi Proyek

Untuk menginisialisasi proyek ada dua cara:

menggunakan cargo init: untuk membuat proyek pada direktori aktif.
menggunakan cargo new: untuk membuat proyek sekaligus membuat, menyiapkan, dan mengisi direktori proyek.

Menggunakan cargo init

$ mkdir hello-cargo
$ cd hello-cargo/
$ cargo init
     Created binary (application) package
$ ls -la 
total 24
drwxr-xr-x 4 zaky zaky 4096 Sep  4 12:12 .
drwxr-xr-x 3 zaky zaky 4096 Sep  4 12:12 ..
-rw-r--r-- 1 zaky zaky  180 Sep  4 12:12 Cargo.toml
drwxr-xr-x 6 zaky zaky 4096 Sep  4 12:12 .git
-rw-r--r-- 1 zaky zaky    8 Sep  4 12:12 .gitignore
drwxr-xr-x 2 zaky zaky 4096 Sep  4 12:12 src
$ tree .
.
├── Cargo.toml
└── src
    └── main.rs

1 directory, 2 files
$

Menggunakan cargo new

$ cargo new hello-cargo-2 --bin
     Created binary (application) `hello-cargo-2` package
$ cd hello-cargo-2/
$ ls -la
total 24
drwxr-xr-x 4 zaky zaky 4096 Sep  4 12:15 .
drwxr-xr-x 4 zaky zaky 4096 Sep  4 12:15 ..
-rw-r--r-- 1 zaky zaky  182 Sep  4 12:15 Cargo.toml
drwxr-xr-x 6 zaky zaky 4096 Sep  4 12:15 .git
-rw-r--r-- 1 zaky zaky    8 Sep  4 12:15 .gitignore
drwxr-xr-x 2 zaky zaky 4096 Sep  4 12:15 src
$ tree .
.
├── Cargo.toml
└── src
    └── main.rs

1 directory, 2 files
$

Catatan: secara default, jika tidak menggunakan parameter, maka rerangka proyek yang dihasilkan adalah rerangka proyek untuk hasil file binary executable atau aplikasi yang bisa dijalankan secara langsung oleh sistem operasi. Jika ingin membuat proyek pustaka / library, gunakan argument --lib sebagai berikut: cargo init --lib atau cargo new project_name --lib.

Secara umum, hasil dari kedua perintah tersebut sama saja.

Struktur Direktori dan Aplikasi Proyek Rust

Suatu proyek Rust yang dihasilkan oleh cargo init maupun cargo new untuk tipe aplikasi maupun pustaka mempunyai struktur yang sama, hanya berbeda di kode sumber src:

Tipe Aplikasi

tree .
.
├── Cargo.toml
└── src
    └── main.rs

1 directory, 2 files
$

Tipe Pustaka

tree .
.
├── Cargo.toml
└── src
    └── lib.rs

1 directory, 2 files
$

Setiap proyek juga mempunyai dua direktori dan file yang tersembunyi (hidden) yang diperlukan oleh Git yaitu direktori .git dan file .gitigore. Direktori .git merupakan direktori internal dari setiap repo Git dan file .gitignore merupakan file yang digunakan untuk memberitahu direktori serta file apa di repo tersebut yang tidak perlu dimasukkan ke repo Git di GitHub atau GitLab. Kedua direktori dan file tersebut muncul karena asumsi bahwa proyek tersebut akan dimasukkan ke suatu repo Git tertentu.

Berikut adalah penjelasan dari struktur direktori serta berbagai file yang ada pada suatu proyek Rust.

Cargo.toml: file ini disebut file manifest dan digunakan untuk mendeskripsikan metadata tentang proyek serta berbagai pustaka yang digunakan di proyek tersebut. File ini dikelola oleh pemrogram.
Cargo.lock: file yang digunakan secara internal oleh cargo untuk mengelola seluruh pustaka yang digunakan di proyek tersebut. File ini tidak dimaksudkan untuk dikelola oleh pemrogram. File ini akan muncul jika pemrogram sudah melakukan proses membangun aplikasi (build).
src: tempat pemrogram menempatkan kode sumber. Jika aplikasi, maka akan bernama main.rs yang akan menjadi titik awal eksekusi program.
target: direktori hasil proses kompilasi, akan muncul jika sudah dilakukan proses kompilasi / membangun / build.

Catatan: jika proyek merupakan proyek untuk pustaka selain pustaka sistem (yang menggunakan tipe crate staticlib atau cdylib), masukkan Cargo.lock ke baris di .gitignore. Selain itu, jangan masukkan.

Suatu file Cargo.toml biasanya berisi minimal:

[package]
name = "hello-cargo-2"
version = "0.1.0"
edition = "2018"

# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html

[dependencies]

File Cargo.toml mempunyai format TOML dan secara minimal berisi deskripsi:

package: menjelaskan tentang paket proyek tersebut, minimal berisi name (nama proyek), version (versi proyek), dan edition (edisi Rust yang digunakaan).
dependencies: berbagai pustaka yang digunakan di aplikasi serta versinya.

Membangun Proyek

Untuk membangun proyek, cargo harus dikerjakan pada direktori tempat proyek tersebut berada. Ada 2 kategori proyek yang dibangun:

Versi debug / dev
Versi release

Versi debug menyertakan data untuk proses debugging sehingga ukurannya lebih besar. Saat pengembangan, biasanya proses membangun proyek dilakukan secara default menggunakan versi debug. Jika proyek sudah selesai, maka dibangun menggunakan versi release. Berikut adalah proses serta hasil dari masing-masing versi.

Versi Debug

$ cargo build
   Compiling hello-cargo-2 v0.1.0 (/home/zaky/kerjaan/src/rust/hello-cargo-2)
    Finished dev [unoptimized + debuginfo] target(s) in 8.53s
$ tree 
Cargo.lock  Cargo.toml  .git/       .gitignore  src/        target/     
$ tree target/
target/
├── CACHEDIR.TAG
└── debug
    ├── build
    ├── deps
    │   ├── hello_cargo_2-61ab1226333d611e
    │   └── hello_cargo_2-61ab1226333d611e.d
    ├── examples
    ├── hello-cargo-2
    ├── hello-cargo-2.d
    └── incremental
        └── hello_cargo_2-1tf9vp8hw5tph
            ├── s-g21ocip69e-1gz7gsu-2d3iv3pzmnper
            │   ├── 14ljyy7cs4njs43i.o
            │   ├── 1jvulq62qig4vscu.o
            │   ├── 28iowghk4bcm6y1h.o
            │   ├── 3okkrcxho0rd7dc2.o
            │   ├── 46r7u1vfzs5zeczg.o
            │   ├── 50jgk6qv50atsv1.o
            │   ├── dep-graph.bin
            │   ├── dhg43ne52kxn1e6.o
            │   ├── query-cache.bin
            │   ├── sn76ibo0w8dil4z.o
            │   └── work-products.bin
            └── s-g21ocip69e-1gz7gsu.lock

7 directories, 17 files
$ $ du -h target/debug/
3,2M    target/debug/deps
4,0K    target/debug/examples
564K    target/debug/incremental/hello_cargo_2-1tf9vp8hw5tph/s-g21ocip69e-1gz7gsu-2d3iv3pzmnper
568K    target/debug/incremental/hello_cargo_2-1tf9vp8hw5tph
572K    target/debug/incremental
20K target/debug/.fingerprint/hello-cargo-2-61ab1226333d611e
24K target/debug/.fingerprint
4,0K    target/debug/build
3,8M    target/debug/
$

Hasil dari membangun aplikasi menggunakan versi debug adalah:

Direktori target/debug sebesar 3,8 MB
Hasil kompilasi utama:

$ ls -la target/debug/hello-cargo-2
-rwxr-xr-x 2 zaky zaky 3290088 Sep  4 12:21 target/debug/hello-cargo-2`
$

Versi Release

$ cargo build --release
   Compiling hello-cargo-2 v0.1.0 (/home/zaky/kerjaan/src/rust/hello-cargo-2)
    Finished release [optimized] target(s) in 0.54s
$ tree target/release/
target/release/
├── build
├── deps
│   ├── hello_cargo_2-0904ddb38520974e
│   └── hello_cargo_2-0904ddb38520974e.d
├── examples
├── hello-cargo-2
├── hello-cargo-2.d
└── incremental

4 directories, 4 files
$ du -h target/release/
3,2M    target/release/deps
4,0K    target/release/examples
4,0K    target/release/incremental
20K target/release/.fingerprint/hello-cargo-2-0904ddb38520974e
24K target/release/.fingerprint
4,0K    target/release/build
3,2M    target/release/
$

Hasil dari membangun aplikasi menggunakan versi release adalah:

Direktori target/release sebesar 3,2 MB
Hasil kompilasi utama:

$ ls -la target/release/hello-cargo-2
-rwxr-xr-x 2 zaky zaky 3280008 Sep  4 16:00 target/release/hello-cargo-2
$

Dari apa yang telah dihasilkan tersebut, kita bisa mengetahui bahwa versi release mempunyai ukuran lebih kecil serta waktu kompilasi yang lebih cepat daripada versi debug.

Menjalankan Hasil

Untuk menjalankan hasil, hasil utama kompilasi bisa dieksekusi secara langsung, atau bisa juga menggunakan cargo run.

$ target/debug/hello-cargo-2 
Hello, world!
$ target/release/hello-cargo-2 
Hello, world!
$ cargo run 
    Finished dev [unoptimized + debuginfo] target(s) in 0.00s
     Running `target/debug/hello-cargo-2`
Hello, world!
$ cargo run --release
    Finished release [optimized] target(s) in 0.00s
     Running `target/release/hello-cargo-2`
Hello, world!
$

Menggunakan `cargo` untuk Mengelola Dependencies

Seperti yang telah dijelaskan di awal, cargo bisa digunakan untuk mengelola berbagai pustaka yang diperlukan. Pengelolaan ini dilakukan menggunakan file Cargo.toml. Berikut ini kita akan membuat aplikasi yang memanfaatkan suatu pustaka dari https://crates.io.

Aplikasi yang kita buat merupakan aplikasi untuk mengkonversi warna 4-bit sRGB dan warna palet 8-bit yang digunakan oleh terminal ANSI (xterm, rxvt-unicode) ke dalam mode warna 256.

Catatan: penggunakan crate pada bagian ini hanya merupakan contoh saja. Hal yang perlu diperhatikan adalah cara menggunakan crate / pustaka. Mengenai pemanfaatan pustakan dan kode sumber, tidak perlu dipahami.

Crate yang digunakan bisa diperoleh di https://crates.io/crates/ansi_colours. Masukkan dependensi ini ke Cargo.toml:

[package]
name = "hello-time"
version = "0.1.0"
edition = "2018"

# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html

[dependencies]
ansi_colours = "1.0.4"

Kompilasi bisa dilakukan seperti biasa. Saat proses membangun aplikasi, cargo akan mengambil dan mengelola pustaka / crate yang sudah kita spesifikasikan.

$ cargo build --release
    Updating crates.io index
  Downloaded ansi_colours v1.0.4
  Downloaded cc v1.0.70
  Downloaded 2 crates (67.7 KB) in 0.87s
   Compiling cc v1.0.70
   Compiling ansi_colours v1.0.4
   Compiling hello-time v0.1.0 (/home/zaky/kerjaan/src/rust/hello-time)
    Finished release [optimized] target(s) in 4.69s
$ cargo run --release
    Finished release [optimized] target(s) in 0.00s
     Running `target/release/hello-time`
 50: (0, 255, 215)
(100, 200, 150) ~  78 (95, 215, 135)
$

Membersihkan Hasil Kompilasi

Jika kita ingin membersihkan direktori proyek dari hasil kompilasi, gunakan perintah cargo clean di direktori proyek tersebut.

Clippy

Clippy digunakan sebagai linter dan digunakan untuk menangkap berbagai kemungkinan error yang umum maupun berbagai perbaikan yang bisa digunakan untuk memperbaiki kode sumber kita (meski tidak terdapat error). Untuk menggunakan clippy, maka clippy harus terinstall - biasanya sudah diinstall saat menginstall Rust menggunakan rustup. Jika belum terinstall, gunakan:

$ rustup component add clippy

Contoh penggunaaan clippy pada proyek hello-cargo-2 di atas:

$ cargo clippy --release
    Checking hello-cargo-2 v0.1.0 (/home/zaky/kerjaan/src/rust/hello-cargo-2)
    Finished release [optimized] target(s) in 0.03s
$

Misal, kita buat error dengan sengaja di src/main.rs dengan menghapus penutup string:

fn main() {
    println!("Hello, world!);
}

Kita bisa menggunakan clippy berikut ini:

$ cargo clippy --release
    Checking hello-cargo-2 v0.1.0 (/home/zaky/kerjaan/src/rust/hello-cargo-2)
error[E0765]: unterminated double quote string
 --> src/main.rs:2:14
  |
2 |       println!("Hello, world!);
  |  ______________^
3 | | }
  | |__^

error: aborting due to previous error

For more information about this error, try `rustc --explain E0765`.
error: could not compile `hello-cargo-2`

To learn more, run the command again with --verbose.
$

Pada bagian awal seperti ini, error serta saran yang muncul sama dengan saat menggunakan cargo build, tetapi semakin kompleks kesalahan serta kode sumber, maka clippy akan memberikan masukan yang lebih baik. Pada posisi ini, pahami penggunaan clippy.

Mengikuti Perkembangan Rust

Perkembangan Rust sangat menarik dan dinamis. Berikut ini adalah beberapa tempat yang bisa menjadi panduan untuk mengikuti perkembangan dari Rust.

This Week in Rust: newsletter mingguan tentang perkembangan Rust
Awesome Rust.
Not-Yet-Awesome Rust: software, kode sumber, maupun berbagai sumber daya yang belum ada di Rust meski sangat diperlukan.
Komunitas Rust
Cari tags Rust di StackOverflow.

Belajar Rust - 01: Mengenal Bahasa Pemrograman Rust

Bambang Purnomosidi D. P. — Sat, 28 Aug 2021 22:55:30 +0000

Bagian ini membahas tentang gambaran umum dari bahasa pemrograman serta peranti pengembangan Rust. Dengan mempelajari bab ini, pembaca diharapkan bisa memahami gambaran umum dari Rust sehingga bisa memberikan semacam pemahaman terhadap ruang lingkup masalah-masalah pemrograman yang bisa diselesaikan menggunakan Rust serta posisi Rust di antara berbagai bahasa pemrograman dan peranti pengembangan lainnya.

Apakah Rust Itu?

Secara umum, biasanya para pemrograman akan menyebut Rust untuk segala macam peranti pengembangan yang terkait dengan Rust. Pada dasarnya, saat membicarakan tentang peranti pengembangan, ada beberapa komponen sebagai berikut:

Spesifikasi bahasa pemrograman
Implementasi bahasa pemrograman dalam bentuk compiler / interpreter
Package Manager yang digunakan untuk mengelola pustaka / paket yang diperlukan saat dilakukan proses kompilasi maupun untuk instalasi berbagai peranti pendukung yang dibutuhkan pemrogram saat membangun aplikasi.
Build Tool yang digunakan untuk mengelola proses kompilasi serta hasil akhirnya.

Hal tersebut juga berlaku untuk Rust. Meskipun seringkali hanya disebut Rust, biasanya sudah mengacu ke setidaknya spesifikasi bahasa pemrograman Rust serta compiler dari Rust. Pada pembahasan ini, penyebutan Rust akan mengacu pada spesifikasi bahasa pemrograman serta peranti standar untuk compiler maupun pustaka standar yang disertakan pada saat instalasi Rust. Informasi tentang Rust bisa diperoleh di Web bahasa pemrograman Rust

Sejarah Singkat Rust

Rust pertama kali dibuat oleh salah seorang pegawai dari Mozilla yang bernama Graydon Hoare sekitar tahun 2006. Saat itu, Graydon membuat bahasa pemrograman baru dan compiler dari bahasa pemrograman tersebut menggunakan OCaml.
Mozilla mulai men-sponsori dan mendukung Rust untuk keperluan internal pada tahun 2009 (diumumkan tahun 2010).
Tahun 2010, pengembangan Rust menggunakan OCaml dihentikan, digantikan dengan self-hosting compiler (Rust dibuat dengan menggunakan Rust). Tahun 2011, Rust berhasil digunakan untuk mengkompilasi dirinya sendiri. Saat itu, Rust menggunakan LLVM sbagai compiler backend.
Versi stabil pertama (versi 1.0.0) dari Rust berhasil dirilis pada tanggal 15 Mei 2015.
Setelah itu, Rust menetapkan pola rilis pasti setiap 6 minggu, artinya setiap 6 minggu ada rilis baru untuk versi stabil, beta, dan nightly.

Paradigma Pemrograman Rust

Paradigma pemrograman merupakan cara pandang untuk menyelesaikan permasalahan pemrograman. Rust tidak mempunyai suatu paradigma pemrograman spesifik tertentu, tetapi lebih ke arah multi-paradigm atau mempunyai lebih dari satu paradigma. Secara umum, paradigma pemrograman Rust adalah:

Konkuren: mendukung pemrograman secara konkuren, artinya lebih dari satu unit komputasi bisa dieksekusi secara "bersamaan" (secara overlap, bergantian - tidak harus menunggu satu unit komputasi selesai baru kemudian satu unit komputasi berikutnya dieksekusi.
Fungsional: program dikonstruksi dengan menggunakan melakukan komposisi function.
Generik: tipe pada fungsi bisa dispesifikasikan belakangan, bukan pada saat pembuatan fungsi.
Imperatif: program terdiri atas berbagai statement yang mengubah state dari program (misal dengan memanipulasi variabel, dan lain-lain).
Terstruktur: program menekankan pada penggunakan berbagai struktur kendali serta subprogram, terutama digunakan untuk readibility.
PBO (Pemrograman Berorientasi Obyek): meski Rust tidak murni bahasa PBO, tetapi Rust mendukung berbagai fitur PBO yang memungkinkan pemrogram untuk mengkonstruksi program dengan pendekatan obyek yang mempunyai karakteristik serta perilaku tertentu dan adanya interaksi antar obyek tersebut dalam menyelesaikan masalah pemrograman.

Lisensi Rust

Semua artifak dari Rust (compiler, logo, situs Web, dan lain-lain) mempunyai lisensi ganda:

MIT License
Apache License - Versi 2.0

Software yang Dibangun Menggunakan Rust

Rust digunakan untuk membangun berbagai software, mulai dari low level sampai dengan high level. Istilah low level dan high level ini digunakan untuk menunjukkan kedekatan dengan akses mesin. Low level dikenal juga dengan istilah system programming (meski istilah ini bukan merupakan istilah yang kanonikal). Rust merupakan satu di antara sedikit bahasa pemrograman dan peranti pengembangan yang bisa digunakan utk semua level. Bagian ini menunjukkan beberapa software yang dibangun dengan menggunakan Rust.

Servo: engine penjelajah Web (Web browser) yang digunakan dalam browser Mozilla Firefox melalui proyek Quantum.
Redox: sistem operasi baru dengan teknologi microkernel dengan userland mirip Unix.
Nushell: shell.
TiKV: basis data key-value transaksional yang terdistribusi.
Deno: runtime untuk JavaScript dan TypeScript.
Discord: salah satu peranti pengembangan yang digunakan untuk mengembangkan sistem Discord.

Domain Masalah dari Rust

Rust bisa digunakan untuk menyelesaikan berbagai masalah pada berbagai domain. Secara umum, Rust bisa digunakan untuk pembuatan software di aras rendah (system programming) maupun di berbagai masalah pemrograman aras atas. Beberapa domain masalah yang bisa diselesaikan oleh Rust antara lain:

System Programming
Akses ke peranti keras (interfacing)
CLI (Command Line Interface)
Backend
Aplikasi Web
Akses ke berbagai basis data
GUI (Graphical User Interface)
Cloud

Using YugabyteDB in Python App Development

Bambang Purnomosidi D. P. — Sat, 28 Aug 2021 09:47:01 +0000

As a long time PostgreSQL user, it's normal that YugabyteDB got my attention. It's a distributed SQL database which features-compatible with PostgreSQL so that I don't need to lose my investation. YugabyteDB reuses PostgreSQL's query layer, so I can use my development tools as usual. It gives me more since there is also Cassandra query layer. Using YugabyteDB I can reuse my SQL skill and development tools, enhanced with NOSQL data model (especially wide-column store), while I have NewSQL's resiliency, scalability, and high performance.

In this article, I am going to setup YugabyteDB for local cluster, populate data, and access the data using Python3.

Install and Configure YugabyteDB

Installation is very easy and straightforward. No source code compilation (well, unless you really want to dig that deep). Just download YugabyteDB, extract, then execute bin/post-install.sh. When this step has finished, make sure that path/to/extracted/yugabytedb/bin is in the $PATH. Here's what I did:

Fish Shell

$ set -x path/to/extracted/yugabytedb/bin $PATH

Bash Shell

$ export PATH=path/to/extracted/yugabytedb/bin:$PATH

Note: to avoid writing the same thing over and over again, I usually put the set or export statements above inside a file and then whenever I want to use YugabyteDB, I just source the-file.sh.

Next, we need to configure YugabyteDB. To configure YugabyteDB, see YugabyteDB configuration. The documentation is complete but to have everything works, all I need to do is changing /etc/security/limits.conf to:

# /etc/security/limits.conf
#
#Each line describes a limit for a user in the form:
...
...
...
#<domain>      <type>  <item>         <value>
#

*                -       core            unlimited
*                -       data            unlimited
*                -       fsize           unlimited
*                -       sigpending      119934
*                -       memlock         64
*                -       rss             unlimited
*                -       nofile          1048576
*                -       msgqueue        819200
*                -       stack           8192
*                -       cpu             unlimited
*                -       nproc           12000
*                -       locks           unlimited

# End of file

Depends on your situation, maybe you need to restart or just logout-login back.

All data, logs, configurations, etc for YugabyteDB reside in $HOME/var/. Do check $HOME/var/conf/yugabytedb.conf for more configuration:

{
    "tserver_webserver_port": 9000, 
    "master_rpc_port": 7100, 
    "universe_uuid": "dabc3d28-6982-4585-8b10-5faa7352da02", 
    "webserver_port": 7200, 
    "ysql_enable_auth": false, 
    "cluster_member": true, 
    "ycql_port": 9042, 
    "data_dir": "/home/bpdp/var/data", 
    "tserver_uuid": "71ad70b8eef149ae945842572e0fff75", 
    "use_cassandra_authentication": false, 
    "log_dir": "/home/bpdp/var/logs", 
    "polling_interval": "5", 
    "listen": "0.0.0.0", 
    "callhome": true, 
    "master_webserver_port": 7000, 
    "master_uuid": "1ef618e573a04e1d835f4ed4364825d7", 
    "master_flags": "", 
    "node_uuid": "6ae31951-7199-4c22-b30b-e8f235cef7db", 
    "join": "", 
    "ysql_port": 5433, 
    "tserver_flags": "", 
    "tserver_rpc_port": 9100
}

Note: PostgreSQL usually uses port 5432, but YugabyteDB default port is 5433. Pay attention to this since we are going to use this when we write our code.

So many things we can do with YugabyteDB, but for this article, I will concentrate more on Python app development. Therefore, it's enough now to have local cluster. Let's set it up!.

Let's run YugabyteDB:

$ yugabyted start
Starting yugabyted...
✅ System checks           

+--------------------------------------------------------------------------------------------------+
|                                            yugabyted                                             |
+--------------------------------------------------------------------------------------------------+
| Status              : Running. Leader Master is present                                          |
| Web console         : http://127.0.0.1:7000                                                      |
| JDBC                : jdbc:postgresql://127.0.0.1:5433/yugabyte?user=yugabyte&password=yugabyte  |
| YSQL                : bin/ysqlsh   -U yugabyte -d yugabyte                                       |
| YCQL                : bin/ycqlsh   -u cassandra                                                  |
| Data Dir            : /home/bpdp/var/data                                                        |
| Log Dir             : /home/bpdp/var/logs                                                        |
| Universe UUID       : dabc3d28-6982-4585-8b10-5faa7352da02                                       |
+--------------------------------------------------------------------------------------------------+
🚀 yugabyted started successfully! To load a sample dataset, try 'yugabyted demo'.
🎉 Join us on Slack at https://www.yugabyte.com/slack
👕 Claim your free t-shirt at https://www.yugabyte.com/community-rewards/
$

Check the status:

$ yugabyted status

+--------------------------------------------------------------------------------------------------+
|                                            yugabyted                                             |
+--------------------------------------------------------------------------------------------------+
| Status              : Running. Leader Master is present                                          |
| Web console         : http://127.0.0.1:7000                                                      |
| JDBC                : jdbc:postgresql://127.0.0.1:5433/yugabyte?user=yugabyte&password=yugabyte  |
| YSQL                : bin/ysqlsh   -U yugabyte -d yugabyte                                       |
| YCQL                : bin/ycqlsh   -u cassandra                                                  |
| Data Dir            : /home/bpdp/var/data                                                        |
| Log Dir             : /home/bpdp/var/logs                                                        |
| Universe UUID       : dabc3d28-6982-4585-8b10-5faa7352da02                                       |
+--------------------------------------------------------------------------------------------------+

Just in case you need to shutdown YugabyteDB:

$ yugabyted stop
Stopped yugabyted using config /home/bpdp/var/conf/yugabyted.conf.
$

Ok, now let YugabyteDB runs. We will use that for later processes.

Data Preparation

Now, it gets more interesting. Using one YugabyteDB server instance, we can use both SQL and Cassandra data model. Let's aggregate some data into PostgreSQL layer and Cassandra layer. For this purpose, we still use default user and password. Later on, you can manage the security side of YugabyteDB.

Note: default username and password for PostgreSQL layer: yugabyte:yugabyte, while for Cassandra: cassandra:cassandra.

SQL Data

YugabyteDB provides sample datasets for SQL data. We are going to use Northwind Traders Database. Get the DDL and Data scripts from the Northwind sample datasets URL. Follow this sceen dump to prepare the database, tables, and populate the data. The # pompt is the place to write command.

$ ysqlsh -U yugabyte
ysqlsh (11.2-YB-2.7.2.0-b0)
Type "help" for help.

yugabyte=# create database northwind;
CREATE DATABASE
yugabyte=# \l
                                   List of databases
      Name       |  Owner   | Encoding | Collate |    Ctype    |   Access privileges   
-----------------+----------+----------+---------+-------------+-----------------------
 northwind       | yugabyte | UTF8     | C       | en_US.UTF-8 | 
 postgres        | postgres | UTF8     | C       | en_US.UTF-8 | 
 system_platform | postgres | UTF8     | C       | en_US.UTF-8 | 
 template0       | postgres | UTF8     | C       | en_US.UTF-8 | =c/postgres          +
                 |          |          |         |             | postgres=CTc/postgres
 template1       | postgres | UTF8     | C       | en_US.UTF-8 | =c/postgres          +
                 |          |          |         |             | postgres=CTc/postgres
 yugabyte        | postgres | UTF8     | C       | en_US.UTF-8 | 
(6 rows)

yugabyte=# \c northwind
You are now connected to database "northwind" as user "yugabyte".
northwind=# \i northwind_ddl.sql 
SET
SET
SET
SET
SET
SET
SET
SET
DROP TABLE
DROP TABLE
DROP TABLE
DROP TABLE
DROP TABLE
DROP TABLE
DROP TABLE
DROP TABLE
DROP TABLE
DROP TABLE
DROP TABLE
DROP TABLE
DROP TABLE
DROP TABLE
CREATE TABLE
CREATE TABLE
CREATE TABLE
CREATE TABLE
CREATE TABLE
CREATE TABLE
CREATE TABLE
CREATE TABLE
CREATE TABLE
CREATE TABLE
CREATE TABLE
CREATE TABLE
CREATE TABLE
CREATE TABLE
northwind=# \d
                 List of relations
 Schema |          Name          | Type  |  Owner   
--------+------------------------+-------+----------
 public | categories             | table | yugabyte
 public | customer_customer_demo | table | yugabyte
 public | customer_demographics  | table | yugabyte
 public | customers              | table | yugabyte
 public | employee_territories   | table | yugabyte
 public | employees              | table | yugabyte
 public | order_details          | table | yugabyte
 public | orders                 | table | yugabyte
 public | products               | table | yugabyte
 public | region                 | table | yugabyte
 public | shippers               | table | yugabyte
 public | suppliers              | table | yugabyte
 public | territories            | table | yugabyte
 public | us_states              | table | yugabyte
(14 rows)

northwind=# \i northwind_data.sql
...
...
...
INSERT 0 1
INSERT 0 1
INSERT 0 1
northwind=# select * from products;
 product_id |           product_name           | supplier_id | category_id |  quantity_per_unit   | unit_price | units_in_s
tock | units_on_order | reorder_level | discontinued 
------------+----------------------------------+-------------+-------------+----------------------+------------+-----------
-----+----------------+---------------+--------------
          4 | Chef Anton's Cajun Seasoning     |           2 |           2 | 48 - 6 oz jars       |         22 |           
  53 |              0 |             0 |            0
         46 | Spegesild                        |          21 |           8 | 4 - 450 g glasses    |         12 |           
  95 |              0 |             0 |            0
         73 | Röd Kaviar                       |          17 |           8 | 24 - 150 g jars      |         15 |           
 101 |              0 |             5 |            0
         29 | Thüringer Rostbratwurst          |          12 |           6 | 50 bags x 30 sausgs. |     123.79 |           
   0 |              0 |             0 |            1
         70 | Outback Lager                    |           7 |           1 | 24 - 355 ml bottles  |         15 |           
  15 |             10 |            30 |            0
         25 | NuNuCa Nuß-Nougat-Creme          |          11 |           3 | 20 - 450 g glasses   |         14 |           
  76 |              0 |            30 |            0
         54 | Tourtière                        |          25 |           6 | 16 pies              |       7.45 |           
  21 |              0 |            10 |            0
...
...
...
         17 | Alice Mutton                     |           7 |           6 | 20 - 1 kg tins       |         39 |           
   0 |              0 |             0 |            1
         59 | Raclette Courdavault             |          28 |           4 | 5 kg pkg.            |         55 |           
  79 |              0 |             0 |            0
(77 rows)

northwind=#

Finish with SQL data, it's about the time to populate column-wide - Cassandra data.

NOSQL Column-wide Data - Apache Cassandra

We will use a simple keyspace: one keyspace, consists of one table. Create a CQL script file (here, the file name is zimera-employees.cql):

CREATE KEYSPACE zimera
  WITH replication = {'class':'SimpleStrategy', 'replication_factor' : 3};

USE zimera;

CREATE TABLE employees(
   e_id int PRIMARY KEY,
   e_fullname text,
   e_address text,
   e_dept text,
   e_role text
   );

INSERT INTO employees (e_id, e_fullname, e_address, e_dept, e_role) VALUES(1,'Zaky A. Aditya', 'Dusun Medelan, RT 01, Umbulmartani, Ngemplak, Sleman, DIY, Indonesia', 'Information Technology', 'Machine Learning Developer');

Execute the script:

$ ycqlsh -f zimera-employees.cql 
$

Check whether succeed or not:

$ ycqlsh -u cassandra
Password: 
Connected to local cluster at 127.0.0.1:9042.
[ycqlsh 5.0.1 | Cassandra 3.9-SNAPSHOT | CQL spec 3.4.2 | Native protocol v4]
Use HELP for help.
cassandra@ycqlsh> use zimera;
cassandra@ycqlsh:zimera> select * from employees;

 e_id | e_fullname     | e_address                                                            | e_dept                 | e_role
------+----------------+----------------------------------------------------------------------+------------------------+----------------------------
    1 | Zaky A. Aditya | Dusun Medelan, RT 01, Umbulmartani, Ngemplak, Sleman, DIY, Indonesia | Information Technology | Machine Learning Developer

(1 rows)
cassandra@ycqlsh:zimera> 
$

Python - Drivers

Since we are going to use both PostgreSQL and Apache Cassandra data model, we need to install those two drivers: psycopg2 for PostgreSQL and Python Driver for Apache Cassandra.

Note: currently, psycopg is still developing psycopg3. We do not use psycopg3 since it is still in early development stage, but once psycopg3 is released, there should be easy to migrate.

Install Cassandra Driver

$ conda install cassandra-driver
...
...
...
  added / updated specs:
    - cassandra-driver


The following packages will be downloaded:

    package                    |            build
    ---------------------------|-----------------
    cassandra-driver-3.25.0    |   py39h27cfd23_0         3.0 MB
    ------------------------------------------------------------
                                           Total:         3.0 MB

The following NEW packages will be INSTALLED:

  blas               pkgs/main/linux-64::blas-1.0-mkl
  cassandra-driver   pkgs/main/linux-64::cassandra-driver-3.25.0-py39h27cfd23_0
  intel-openmp       pkgs/main/linux-64::intel-openmp-2021.3.0-h06a4308_3350
  libev              pkgs/main/linux-64::libev-4.33-h7b6447c_0
  mkl                pkgs/main/linux-64::mkl-2021.3.0-h06a4308_520
  mkl-service        pkgs/main/linux-64::mkl-service-2.4.0-py39h7f8727e_0
  mkl_fft            pkgs/main/linux-64::mkl_fft-1.3.0-py39h42c9631_2
  mkl_random         pkgs/main/linux-64::mkl_random-1.2.2-py39h51133e4_0
  numpy              pkgs/main/linux-64::numpy-1.20.3-py39hf144106_0
  numpy-base         pkgs/main/linux-64::numpy-base-1.20.3-py39h74d4b33_0
  six                pkgs/main/noarch::six-1.16.0-pyhd3eb1b0_0


Proceed ([y]/n)? y
...
...
...
$

Install PostgreSQL Driver

$ conda install psycopg2                                                              ...
...
...
  added / updated specs:
    - psycopg2


The following NEW packages will be INSTALLED:

  krb5               pkgs/main/linux-64::krb5-1.19.2-hac12032_0
  libedit            pkgs/main/linux-64::libedit-3.1.20210714-h7f8727e_0
  libpq              pkgs/main/linux-64::libpq-12.2-h553bfba_1
  psycopg2           pkgs/main/linux-64::psycopg2-2.8.6-py39h3c74f83_1


Proceed ([y]/n)? y
...
...
$

Note: I use conda for package management, but you don't need to. You can also use pip, in this case just pip install psycopg2 and pip install cassandra-driver.

Let's Code!

Accessing SQL Data

# code-sql.py
import psycopg2

conn = psycopg2.connect(
    host="localhost",
    database="northwind",
    user="yugabyte",
    port="5433",
    password="yugabyte")

# Open a cursor to perform database operations
cur = conn.cursor()

# Execute a query
cur.execute("SELECT * FROM products")

# Retrieve query results
records = cur.fetchall()
print(records[0])

Results:

$ python code-sql.py
(4, "Chef Anton's Cajun Seasoning", 2, 2, '48 - 6 oz jars', 22.0, 53, 0, 0, 0)
$

Accessing Cassandra Data Model

from cassandra.cluster import Cluster

cluster = Cluster()
session = cluster.connect('zimera')

rows = session.execute('SELECT e_fullname, e_address, e_dept, e_role FROM employees')
for row in rows:
    print(row.e_fullname, row.e_address, row.e_dept, row.e_role)

Results:

$ python code-cassandra.py 
Zaky A. Aditya Dusun Medelan, RT 01, Umbulmartani, Ngemplak, Sleman, DIY, Indonesia Information Technology Machine Learning Developer
$

What if we want to use both data model in one python source code? Here you go:

# code-all.py
import psycopg2
from cassandra.cluster import Cluster

conn = psycopg2.connect(
    host="localhost",
    database="northwind",
    user="yugabyte",
    port="5433",
    password="yugabyte")

# Open a cursor to perform database operations
cur = conn.cursor()

# Execute a query
cur.execute("SELECT * FROM products")

# Retrieve query results
records = cur.fetchall()
print(records[0])

cluster = Cluster()
session = cluster.connect('zimera')

rows = session.execute('SELECT e_fullname, e_address, e_dept, e_role FROM employees')
for row in rows:
    print(row.e_fullname, row.e_address, row.e_dept, row.e_role)

Results:

$ python code-all.py
(4, "Chef Anton's Cajun Seasoning", 2, 2, '48 - 6 oz jars', 22.0, 53, 0, 0, 0)
Zaky A. Aditya Dusun Medelan, RT 01, Umbulmartani, Ngemplak, Sleman, DIY, Indonesia Information Technology Machine Learning Developer
$

Aren't they cool? Happy coding!

WebSharper: Getting Started Easily

Bambang Purnomosidi D. P. — Wed, 25 Aug 2021 03:49:01 +0000

So I am stuck again when I want to create a web app. Don't laugh. I come from *NIX environment and the way everything is started in WebSharper is quite confusing at first. I tried to go to installation documentation but I don't use Visual Studio nor MonoDevelop. Using paket also doesn't solve my problem since they also seem to use Visual Studio or MonoDevelop.

As someone who used to work in a shell environment, of course using shell is always my preferred way to do something. Then I open the Downloads page which turns out become my saviour.

In short, I have to install template first then using the template to create a skeleton of application and then hack away that skeleton. Easier for me :-D.

Note: make sure you have installed .NET SDK - current version 5.x.x and .NET SDK - LTS version 3.x.x. Read my other article on this matter.

Install Application Template

$ dotnet new -i WebSharper.Templates
Template Name                                 Short Name       Language    Tags                  
--------------------------------------------  ---------------  ----------  ----------------------
Console Application                           console          [C#],F#,VB  Common/Console        
Class library                                 classlib         [C#],F#,VB  Common/Library        
Worker Service                                worker           [C#],F#     Common/Worker/Web     
MSTest Test Project                           mstest           [C#],F#,VB  Test/MSTest           
NUnit 3 Test Item                             nunit-test       [C#],F#,VB  Test/NUnit            
NUnit 3 Test Project                          nunit            [C#],F#,VB  Test/NUnit            
xUnit Test Project                            xunit            [C#],F#,VB  Test/xUnit            
Razor Component                               razorcomponent   [C#]        Web/ASP.NET           
Razor Page                                    page             [C#]        Web/ASP.NET           
MVC ViewImports                               viewimports      [C#]        Web/ASP.NET           
MVC ViewStart                                 viewstart        [C#]        Web/ASP.NET           
Blazor Server App                             blazorserver     [C#]        Web/Blazor            
Bolero Hosted Application                     bolero-app       F#          Web/Blazor/Bolero     
Blazor WebAssembly App                        blazorwasm       [C#]        Web/Blazor/WebAssembly
ASP.NET Core Empty                            web              [C#],F#     Web/Empty             
ASP.NET Core Web App (Model-View-Controller)  mvc              [C#],F#     Web/MVC               
ASP.NET Core Web App                          webapp           [C#]        Web/MVC/Razor Pages   
ASP.NET Core with Angular                     angular          [C#]        Web/MVC/SPA           
ASP.NET Core with React.js                    react            [C#]        Web/MVC/SPA           
ASP.NET Core with React.js and Redux          reactredux       [C#]        Web/MVC/SPA           
Razor Class Library                           razorclasslib    [C#]        Web/Razor/Library     
ASP.NET Core Web API                          webapi           [C#],F#     Web/WebAPI            
ASP.NET Core gRPC Service                     grpc             [C#]        Web/gRPC              
WebSharper 4 Extension                        websharper-ext   F#          WebSharper            
WebSharper 4 Library                          websharper-lib   [C#],F#     WebSharper            
WebSharper 4 Proxy                            websharper-prx   [C#],F#     WebSharper            
WebSharper 4 Client-Server Application        websharper-web   [C#],F#     WebSharper/Web        
WebSharper 4 Html Site                        websharper-html  [C#],F#     WebSharper/Web        
WebSharper 4 Single Page Application          websharper-spa   [C#],F#     WebSharper/Web        
dotnet gitignore file                         gitignore                    Config                
global.json file                              globaljson                   Config                
NuGet Config                                  nugetconfig                  Config                
Dotnet local tool manifest file               tool-manifest                Config                
Web Config                                    webconfig                    Config                
Solution File                                 sln                          Solution              
Protocol Buffer File                          proto                        Web/gRPC              

Examples:
    dotnet new mvc --auth Individual
    dotnet new websharper-lib
    dotnet new --help
    dotnet new websharper-web --help
$

Now we have these templates:

...
...
WebSharper 4 Extension                        websharper-ext   F#          WebSharper            
WebSharper 4 Library                          websharper-lib   [C#],F#     WebSharper            
WebSharper 4 Proxy                            websharper-prx   [C#],F#     WebSharper            
WebSharper 4 Client-Server Application        websharper-web   [C#],F#     WebSharper/Web        
WebSharper 4 Html Site                        websharper-html  [C#],F#     WebSharper/Web        
WebSharper 4 Single Page Application          websharper-spa   [C#],F#     WebSharper/Web        
...
...

Pay attention to the shortname, we are going to use that. To see more information about the templates:

...
...
...
  WebSharper.Templates
    Details:
      NuGetPackageId: WebSharper.Templates
      Version: 4.7.3.424
      Author: IntelliFactory
    Templates:
      WebSharper 4 Client-Server Application (websharper-web) C#
      WebSharper 4 Client-Server Application (websharper-web) F#
      WebSharper 4 Extension (websharper-ext) F#
      WebSharper 4 Library (websharper-lib) C#
      WebSharper 4 Library (websharper-lib) F#
      WebSharper 4 Html Site (websharper-html) C#
      WebSharper 4 Html Site (websharper-html) F#
      WebSharper 4 Proxy (websharper-prx) C#
      WebSharper 4 Proxy (websharper-prx) F#
      WebSharper 4 Single Page Application (websharper-spa) C#
      WebSharper 4 Single Page Application (websharper-spa) F#
    Uninstall Command:
      dotnet new -u WebSharper.Templates
$

There are 6 types of templates:

Client-Server Application / websharper-web: full client-server application - in other world, it is usually called fullstack.
Extension / websharper-ext: interface to an existing JS library.
Library / websharper-lib: library which can be used in any WebSharper project.
HTML Site / websharper-html: multipage HTML/JavaScript application.
Proxy / websharper-prx: JavaScript-compilable F# implementations for classes and modules that were compiled without WebSharper.
Single Page Application / websharper-spa: single page HTML/JavaScript with HTML and F# contents plugs into it.

As an example, I will use SPA template to create a skeleton of SPA project. Here's how to do that:

$ dotnet new websharper-spa -lang f# -n helloSPA
The template "WebSharper 4 Single Page Application" was created successfully.
...
...

Note: helloSPA is project name which later becomes application name.

Here's the results:

$ cd helloSPA
$ ls -la
total 28
drwxr-xr-x 3 bpdp bpdp 4096 Agu 25 10:19 ./
drwxr-xr-x 3 bpdp bpdp 4096 Agu 25 10:19 ../
-rw-r--r-- 1 bpdp bpdp 1019 Agu 25 10:19 Client.fs
-rw-r--r-- 1 bpdp bpdp  599 Agu 25 10:19 helloSPA.fsproj
-rw-r--r-- 1 bpdp bpdp 1045 Agu 25 10:19 Startup.fs
-rw-r--r-- 1 bpdp bpdp  123 Agu 25 10:19 wsconfig.json
drwxr-xr-x 2 bpdp bpdp 4096 Agu 25 10:19 wwwroot/
$

That's it. Now we have a skeleton of SPA app. Let's try to run it.

$ dotnet run
Hosting environment: Production
Content root path: /home/bpdp/kerjaan/src/fsharp/websharper/artikel/helloSPA
Now listening on: http://localhost:5000
Now listening on: https://localhost:5001
Application started. Press Ctrl+C to shut down.

Open http://localhost:5000 using your browser:

Voila! you have WebSharper up and running. Now, what you need to do is to understand the contents of an SPA app using WebSharper. This one deserves its own articles. At this point, your knowledge on F#, packages / libs, and WebSharper is important.

Update Templates

Whenever there are new releases, we can always update the templates using:

$ dotnet new -i "WebSharper.Templates::*"

Happy coding!

Multiple .NET SDKs and Runtimes Installation

Bambang Purnomosidi D. P. — Sun, 22 Aug 2021 08:52:49 +0000

As a beginner in Microsoft ecosystem, especially under Linux, I found a little bit difficult to get everything works as expected. Last week, I tried to get WebSharper up and run but turns out I can not get it worked. I probably will write about this later. The solution is pretty simple: I need to have .NET SDK - LTS version (3.1.x) while I only have Current version (5.x.x).

So yes, I have to install more than one SDKs and Runtimes. How to do that? dotnet command - AFAIK - can not be used to do that. The answer is dotnet-install scripts - available for Windows and for Bash shell. Using this install script, I can install more than one SDK and Runtimes. Here's how.

Install LTS Version First

The argument --install-dir is used to let installer knows the installation directory.
The argument -c LTS means that we will install latest version from LTS channel

dotnet-install.sh --install-dir ~/software/dotnet-dev-tools/dotnet-all -c LTS
dotnet-install: Note that the intended use of this script is for Continuous Integration (CI) scenarios, where:
dotnet-install: - The SDK needs to be installed without user interaction and without admin rights.
dotnet-install: - The SDK installation doesn't need to persist across multiple CI runs.
dotnet-install: To set up a development environment or to run apps, use installers rather than this script. Visit https://dotnet.microsoft.com/download to get the installer.

dotnet-install: Downloading primary link https://dotnetcli.azureedge.net/dotnet/Sdk/3.1.413/dotnet-sdk-3.1.413-linux-x64.tar.gz
dotnet-install: Extracting zip from https://dotnetcli.azureedge.net/dotnet/Sdk/3.1.413/dotnet-sdk-3.1.413-linux-x64.tar.gz
dotnet-install: Adding to current process PATH: `/home/bpdp/software/dotnet-dev-tools/dotnet-all`. Note: This change will be visible only when sourcing script.
dotnet-install: Note that the script does not resolve dependencies during installation.
dotnet-install: To check the list of dependencies, go to https://docs.microsoft.com/dotnet/core/install, select your operating system and check the "Dependencies" section.
dotnet-install: Installation finished successfully.
$

Install Current Version

Install current version at the same directory location

$ dotnet-install.sh --install-dir ~/software/dotnet-dev-tools/dotnet-all -c Current
dotnet-install: Note that the intended use of this script is for Continuous Integration (CI) scenarios, where:
dotnet-install: - The SDK needs to be installed without user interaction and without admin rights.
dotnet-install: - The SDK installation doesn't need to persist across multiple CI runs.
dotnet-install: To set up a development environment or to run apps, use installers rather than this script. Visit https://dotnet.microsoft.com/download to get the installer.

dotnet-install: Downloading primary link https://dotnetcli.azureedge.net/dotnet/Sdk/5.0.207/dotnet-sdk-5.0.207-linux-x64.tar.gz
dotnet-install: Extracting zip from https://dotnetcli.azureedge.net/dotnet/Sdk/5.0.207/dotnet-sdk-5.0.207-linux-x64.tar.gz
dotnet-install: Adding to current process PATH: `/home/bpdp/software/dotnet-dev-tools/dotnet-all`. Note: This change will be visible only when sourcing script.
dotnet-install: Note that the script does not resolve dependencies during installation.
dotnet-install: To check the list of dependencies, go to https://docs.microsoft.com/dotnet/core/install, select your operating system and check the "Dependencies" section.
dotnet-install: Installation finished successfully.
$

Install versi beta / RC

Jika ingin melakukan instalasi untuk versi yang belum rilis resmi, gunakan channel sesuai dengan nomor rilis versi beta / RC tersebut. Sebagai contoh, saat penulisan artikel ini, versi beta / RC adalah versi 6.0.100-rc1. Berikut ini adalah tampilan saat instalasi:

$ dotnet-install.sh --install-dir ~/software/dotnet-dev-tools/dotnet-all -c 6.0
dotnet-install: Note that the intended use of this script is for Continuous Integration (CI) scenarios, where:
dotnet-install: - The SDK needs to be installed without user interaction and without admin rights.
dotnet-install: - The SDK installation doesn't need to persist across multiple CI runs.
dotnet-install: To set up a development environment or to run apps, use installers rather than this script. Visit https://dotnet.microsoft.com/download to get the installer.

dotnet-install: Downloading primary link https://dotnetcli.azureedge.net/dotnet/Sdk/6.0.100-rc.1.21458.32/dotnet-sdk-6.0.100-rc.1.21458.32-linux-x64.tar.gz
dotnet-install: Extracting zip from https://dotnetcli.azureedge.net/dotnet/Sdk/6.0.100-rc.1.21458.32/dotnet-sdk-6.0.100-rc.1.21458.32-linux-x64.tar.gz
dotnet-install: Adding to current process PATH: `/home/bpdp/software/dotnet-dev-tools/dotnet-all`. Note: This change will be visible only when sourcing script.
dotnet-install: Note that the script does not resolve dependencies during installation.
dotnet-install: To check the list of dependencies, go to https://docs.microsoft.com/dotnet/core/install, select your operating system and check the "Dependencies" section.
dotnet-install: Installation finished successfully.
$

Innstallation Check

Now, when we use --info as dotnet CLI argument, we will have those 2 SDKs and 2 Runtimes already installed:

$ dotnet --info
.NET SDK (reflecting any global.json):
 Version:   6.0.100-rc.1.21458.32
 Commit:    d7c22323c4

Runtime Environment:
 OS Name:     devuan
 OS Version:  4
 OS Platform: Linux
 RID:         linux-x64
 Base Path:   /home/bpdp/software/dotnet-dev-tools/dotnet-all/sdk/6.0.100-rc.1.21458.32/

Host (useful for support):
  Version: 6.0.0-rc.1.21451.13
  Commit:  d7619cd4b1

.NET SDKs installed:
  3.1.413 [/home/bpdp/software/dotnet-dev-tools/dotnet-all/sdk]
  5.0.207 [/home/bpdp/software/dotnet-dev-tools/dotnet-all/sdk]
  6.0.100-rc.1.21458.32 [/home/bpdp/software/dotnet-dev-tools/dotnet-all/sdk]

.NET runtimes installed:
  Microsoft.AspNetCore.App 3.1.19 [/home/bpdp/software/dotnet-dev-tools/dotnet-all/shared/Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 5.0.10 [/home/bpdp/software/dotnet-dev-tools/dotnet-all/shared/Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 6.0.0-rc.1.21452.15 [/home/bpdp/software/dotnet-dev-tools/dotnet-all/shared/Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 3.1.19 [/home/bpdp/software/dotnet-dev-tools/dotnet-all/shared/Microsoft.NETCore.App]
  Microsoft.NETCore.App 5.0.10 [/home/bpdp/software/dotnet-dev-tools/dotnet-all/shared/Microsoft.NETCore.App]
  Microsoft.NETCore.App 6.0.0-rc.1.21451.13 [/home/bpdp/software/dotnet-dev-tools/dotnet-all/shared/Microsoft.NETCore.App]

To install additional .NET runtimes or SDKs:
  https://aka.ms/dotnet-download
$

Now, we can use LTS, Current, and beta / RC version altogether. Enjoy!

Battery Notification in Audio using Fish Shell

Bambang Purnomosidi D. P. — Sat, 21 Aug 2021 08:48:54 +0000

Some desktop environments provide battery notification so that every time battery is low or maybe full, the DE will notify us. The notification usually comes as something like tooltip which may not be handy if we are not in front of our monitor or maybe still concentrate on our tasks. Also, sometimes I want to change my DE or window manager - KDE to GNOME, AwesomeWM to Spectrwm, etc. In this situation I usually stuck. Conky can help but changing WM / DE involves struggling with configuration file(s) and/or more software (panel, for example).

So, that was my problem. I want to have a very simple and can be used to notify my battery status. I decide to use audio to notify myself since it can be used across any DE/WM. All I need to do is just prepare two audio files (you can create that by yourself or download from the Internet) and create this script:

#!/usr/bin/fish

set bcapacity (cat /sys/class/power_supply/BAT0/capacity)
set bstatus (cat /sys/class/power_supply/BAT0/status)

if [ "$bcapacity" -le 15 -a "$bstatus" = "Discharging" ]
  /usr/bin/mpg123 /home/bpdp/Musik/battlow.mp3
end

if [ "$bcapacity" -gt 90 -a "$bstatus" = "Charging" ]
  /usr/bin/mpg123 /home/bpdp/Musik/battfull.mp3
end

Let's say, I put that file in $HOME/bin/batt.sh. I install mpg123 for my player and put those mp3 files at /home/bpdp/Musik/battlow.mp3 for battery low audio and /home/bpdp/Musik/battfull.mp3 for battery full audio.

Put the script into a crontab by crontab -e and write then save this:

*/2 * * * * /home/bpdp/bin/batt.sh

so that every 2 minutes,my battery will be checked. Run cron daemon (I use OpenRC, might be different if you use systemd):

sudo rc-service cron start

That's all.

Getting Started with F# and VSCode in Linux

Bambang Purnomosidi D. P. — Fri, 13 Aug 2021 15:17:19 +0000

F# has become one of the primary programming language on the .NET environment. F# is developed by a non-profit organization: The F# Software Foundation. Don Syme serves as lead designer of F# together with Microsoft Research. Installing .NET SDK means you have F# SDK at your disposal. Here, I will describe how I use Visual Studio Code for F# development. It is intended for beginners who are confused when they first use VSCode with F# (just like me, some time ago).

Install .NET SDK

To install .NET SDK, download the SDK from .NET SDK Download. Download current release and extract them:

$ mkdir ~/sofware/dotnet-5
$ cd ~/software/dotnet-5
$ tar -xvf ~/Downloads/dotnet-sdk-5.0.400-linux-x64.tar.gz
$ ls -la
total 224
drwxr-xr-x 7 bpdp bpdp   4096 Jul 27 01:49 ./
drwxr-xr-x 6 bpdp bpdp   4096 Agu 13 11:27 ../
-rwxr-xr-x 1 bpdp bpdp 133632 Jul 10 01:26 dotnet*
drwxr-xr-x 3 bpdp bpdp   4096 Jul 10 01:28 host/
-rw-r--r-- 1 bpdp bpdp   1116 Jul 10 01:22 LICENSE.txt
drwxr-xr-x 6 bpdp bpdp   4096 Jul 27 01:49 packs/
drwxr-xr-x 3 bpdp bpdp   4096 Jul 27 01:49 sdk/
drwxr-xr-x 4 bpdp bpdp   4096 Jul 16 00:50 shared/
drwxr-xr-x 3 bpdp bpdp   4096 Jul 27 01:49 templates/
-rw-r--r-- 1 bpdp bpdp  60108 Jul 10 01:22 ThirdPartyNotices.txt
$

Now, .NET SDK is installed at ~/software/dotnet-5 directory. We need to tell shell that the new PATH to include the directory location of .NET SDK. I usually put this command inside a file (whatever filename and location, up to you - example here: $HOME/env/dotnet.sh):

Bash

export PATH=$HOME/software/dotnet-5:$PATH

Fish

set -x DOTNET_ROOT $HOME/software/dotnet-5
set PATH $DOTNET_ROOT $PATH

Whenever needed, we can source the file (just once in every shell/terminal):

source ~/env/dotnet.sh

Test that .NET SDK has been installed successfully:

$ dotnet --info
.NET SDK (reflecting any global.json):
 Version:   5.0.400
 Commit:    d61950f9bf

Runtime Environment:
 OS Name:     devuan
 OS Version:  4
 OS Platform: Linux
 RID:         linux-x64
 Base Path:   /home/bpdp/software/dotnet-5/sdk/5.0.400/

Host (useful for support):
  Version: 5.0.9
  Commit:  208e377a53

.NET SDKs installed:
  5.0.400 [/home/bpdp/software/dotnet-5/sdk]

.NET runtimes installed:
  Microsoft.AspNetCore.App 5.0.9 [/home/bpdp/software/dotnet-5/shared/Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 5.0.9 [/home/bpdp/software/dotnet-5/shared/Microsoft.NETCore.App]

To install additional .NET runtimes or SDKs:
  https://aka.ms/dotnet-download
$

We can check wheter we can use F# or not by executing REPL for F# (fsi):

$ dotnet fsi

Microsoft (R) F# Interactive version 11.4.2.0 for F# 5.0
Copyright (c) Microsoft Corporation. All Rights Reserved.

For help type #help;;

>

It all things work, congratulation, you have .NET SDK and F# on your Linux machine. Next, we use VSCode and Ionide for our F# development.

VSCode and Ionide

Visual Studio Code - VSCode is a code editing tools. It provides text editor capabilities and extensible. Many vendor and communities provide extensions for many programming languages. They are all exist at VSCode Marketplace.

Download VSCode and then extract the tarball to a directory:

$ tar -xvf ~/Downloads/code-stable-x64-1628120346.tar.gz
$ mv ~/VSCode-linux-x64 ~/software/

Edit $HOME/env/dotnet.sh which we've already created before (see above). Add this line:

Bash

export PATH=$HOME/software/VSCode-linux-x64/bin:$PATH

Fish

set -x PATH $HOME/software/VSCode-linux-x64/bin $PATH

Close the terminal / shell so that you can source the file later.

Now, install [Ionide] extension for VSCode which will turn VSCode into a fullblown F# IDE. Source the file (open new shell / terminal first):

$ source ~/env/dotnet.sh

Run VScode from shell/terminal using:

$ code

Follow installation instructions at Ionide-fsharp extension. This will also install C# extension since C# extension is Ionide's pre-requisites.

Close VSCode for now.

F# Project at VSCode - Ionide

We can use dotnet command to create a project skeleton, based on a template. Here's some templates:

$ dotnet new --list
Template Name                                 Short Name      Language    Tags                  
--------------------------------------------  --------------  ----------  ----------------------
Console Application                           console         [C#],F#,VB  Common/Console        
Class library                                 classlib        [C#],F#,VB  Common/Library        
Worker Service                                worker          [C#],F#     Common/Worker/Web     
MSTest Test Project                           mstest          [C#],F#,VB  Test/MSTest           
NUnit 3 Test Item                             nunit-test      [C#],F#,VB  Test/NUnit            
NUnit 3 Test Project                          nunit           [C#],F#,VB  Test/NUnit            
xUnit Test Project                            xunit           [C#],F#,VB  Test/xUnit            
Razor Component                               razorcomponent  [C#]        Web/ASP.NET           
Razor Page                                    page            [C#]        Web/ASP.NET           
MVC ViewImports                               viewimports     [C#]        Web/ASP.NET           
MVC ViewStart                                 viewstart       [C#]        Web/ASP.NET           
Blazor Server App                             blazorserver    [C#]        Web/Blazor            
Blazor WebAssembly App                        blazorwasm      [C#]        Web/Blazor/WebAssembly
ASP.NET Core Empty                            web             [C#],F#     Web/Empty             
ASP.NET Core Web App (Model-View-Controller)  mvc             [C#],F#     Web/MVC               
ASP.NET Core Web App                          webapp          [C#]        Web/MVC/Razor Pages   
ASP.NET Core with Angular                     angular         [C#]        Web/MVC/SPA           
ASP.NET Core with React.js                    react           [C#]        Web/MVC/SPA           
ASP.NET Core with React.js and Redux          reactredux      [C#]        Web/MVC/SPA           
Razor Class Library                           razorclasslib   [C#]        Web/Razor/Library     
ASP.NET Core Web API                          webapi          [C#],F#     Web/WebAPI            
ASP.NET Core gRPC Service                     grpc            [C#]        Web/gRPC              
dotnet gitignore file                         gitignore                   Config                
global.json file                              globaljson                  Config                
NuGet Config                                  nugetconfig                 Config                
Dotnet local tool manifest file               tool-manifest               Config                
Web Config                                    webconfig                   Config                
Solution File                                 sln                         Solution              
Protocol Buffer File                          proto                       Web/gRPC              
$

To create a project using a template inside an empty directory:

$ dotnet new console -lang f#

Here's the screendump:

$ mkdir helloFSharp
$ cd helloFSharp/
$ dotnet new console -lang f#
The template "Console Application" was created successfully.

Processing post-creation actions...
Running 'dotnet restore' on /home/bpdp/kerjaan/src/fsharp/helloFSharp/helloFSharp.fsproj...
  Determining projects to restore...
  Restored /home/bpdp/kerjaan/src/fsharp/helloFSharp/helloFSharp.fsproj (in 440 ms).
Restore succeeded.

$ ls -la 
total 20
drwxr-xr-x  3 bpdp bpdp 4096 Agu 13 21:07 ./
drwxr-xr-x 17 bpdp bpdp 4096 Agu 13 21:07 ../
-rw-r--r--  1 bpdp bpdp  282 Agu 13 21:07 helloFSharp.fsproj
drwxr-xr-x  2 bpdp bpdp 4096 Agu 13 21:07 obj/
-rw-r--r--  1 bpdp bpdp  342 Agu 13 21:07 Program.fs
$

From this point, we can run our project using dotnet run:

$ dotnet run
Hello world from F#
$

Are we finish? yes, if we do not use VSCode. Since we will use VSCode for out FSharp IDE, from that directory, do this (of course we have source ~/env/dotnet.sh in this shell / terminal before):

$ code .

Attention: there is dot after code.

Inside VSCode, click on Program.fs so that this file is opened. Run program using F5 key. VSCode will ask for environment. Choose .NET Core:

VSCode will ask some options to launch the compilation process and run the result. launch.json is opened since we do not have that file. The bottom-right of VSCode shows Add Configuration button. Click on that button and choose this:

Change the program from:

"program": "${workspaceFolder}/bin/Debug/<target-framework>/<project-name.dll>",

to this:

"program": "${workspaceFolder}/bin/Debug/dotnet-5/helloFSharp.dll",

Note: see helloFSharp.fsproj file to fill target-framework.

Save the file, and then hit F5 key again. VSCode will display a dialog, shows that we haven't define buld task since we don't have tasks.json file.

Choose Configure task then Create tasks.json file from template, choose .NET Core. VSCode will open tasks.json file. Save file then hit F5. The result can be seen in DEBUG CONSOLE:

Now, we can start our development process. Any new project should have launch.json and tasks.json. They are all saved inside .vscode/ directory:

$ ls -la .vscode/
total 16
drwxr-xr-x 2 bpdp bpdp 4096 Agu 13 21:56 ./
drwxr-xr-x 5 bpdp bpdp 4096 Agu 13 21:30 ../
-rw-r--r-- 1 bpdp bpdp  649 Agu 13 21:51 launch.json
-rw-r--r-- 1 bpdp bpdp  770 Agu 13 21:56 tasks.json
$

There are many possibilities but the most important thing is now we know at least 2 json files and how to create them. Later on, we will modify them, depend on our project requirements.

F# REPL

Ionide also provides FSI:Start from Command pallette (Ctrl-Shift-P) to execute REPL (Read-Eval-Print-Loop):

That's all. Now you may start your F# development, using whatever templates you like and then change launch.json and tasks.json properly.

ERPNext Installation Details

Bambang Purnomosidi D. P. — Wed, 11 Aug 2021 10:28:25 +0000

ERPNext is one of free / open source ERP software available in today's market. Beside their cloud offering, there is a possibility to use ERPNext on-premise. However, installation instructions are not quite clear. I personally have to experiment with installation many times before I got ... "oh this is how things work". I hope, this is not because I am too slow. LOL. So here is my details instruction on how to make ERPNext installed properly.

Preparation

ERPNext is developed in Python using Frappe Framework (will use Frappe term in this article). Both ERPNext and Frappe come from the same company with many community supporters. MariaDB is used for the DBMS, so, before going into details, here is our list of software which I prepare before ERPNext installation:

Python: the programming language to implement Frappe and ERPNext on top of Frappe.
MariaDB: the DBMS, used to store and manage data.
Frappe: software framework, based on Python, used to build ERPNext.
Bench: a CLI program to manage multi-tenant deployments for Frappe apps.
Node.js: JavaScript engine, used by Frappe for frontend purposes.
yarn: package manager for Node.js.
Git: version control system, used by bench CLI.
Redis: personally, I prefer redis-stack, in this article I will use redis-stack 6.2.4.

Installation and Configuration for Infrastructure Software

Python

I use Miniconda distribution. See this installation instructions for information on how to install Miniconda. After installation, create environment - special for this ERPNext installation:



$ conda create -n py310-erpnext python=3.10
$ conda activate py310-erpnext
$ python
Python 3.10.8 (main, Nov  4 2022, 13:48:29) [GCC 11.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>>
$

All of our steps to install ERPNext will be done in this shell. If you want to open another shell, activate conda environment py311-erpnext, just like the command above.

MariaDB

Get MariaDB at https://mariadb.org/download/, install using installation instructions at https://mariadb.com/kb/en/binary-packages/ and then change its configuration (usually you have to edit my.cnf, in most Linux distribution you can find this file in /etc/mysql/my.cnf):



...
[mysqld]
datadir                 = /home/bpdp/mariadbdata
default-storage-engine  = InnoDB
collation-server        = utf8mb4_unicode_ci
character_set_server    = utf8mb4
...

Run MariaDB server process using the instructions at https://mariadb.com/kb/en/starting-and-stopping-mariadb-automatically/.

User root comes with no password, so, I choose to set root password:



mysqladmin -u root password 'root'

Notes: I use root as password for root just for simplicity.

Test your MariaDB installation:



$ mysql -u root -p 
Enter password: 
Welcome to the MariaDB monitor.  Commands end with ; or \g.
Your MariaDB connection id is 5
Server version: 10.10.2-MariaDB MariaDB Server

Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

MariaDB [(none)]> 
$

Frappe

You may read about Frappe at https://github.com/frappe/frappe. In the meantime, this will be installed, together with ERPNext later using bench.

Bench

If you want more information, you can always have a look at its source code here: https://github.com/frappe/bench. Although there are many instructions to install bench, the easiest is just:



$ pip install frappe-bench
Collecting frappe-bench
  Using cached frappe_bench-5.14.4-py3-none-any.whl (145 kB)
Collecting click>=7.0
  Using cached click-8.1.3-py3-none-any.whl (96 kB)
Collecting gitpython~=2.1.15
  Using cached GitPython-2.1.15-py2.py3-none-any.whl (452 kB)
Collecting honcho
  Using cached honcho-1.1.0-py2.py3-none-any.whl (21 kB)
Collecting jinja2~=3.0.3
  Using cached Jinja2-3.0.3-py3-none-any.whl (133 kB)
Collecting python-crontab~=2.6.0
  Using cached python_crontab-2.6.0-py3-none-any.whl
Collecting requests
  Using cached requests-2.28.1-py3-none-any.whl (62 kB)
Collecting semantic-version~=2.8.2
  Using cached semantic_version-2.8.5-py2.py3-none-any.whl (15 kB)
Requirement already satisfied: setuptools>40.9.0 in /home/bpdp/software/python-dev-tools/miniconda39/envs/py311-erpnext/lib/python3.11/site-packages (from frappe-bench) (65.5.1)
Collecting gitdb2<3,>=2
  Using cached gitdb2-2.0.6-py2.py3-none-any.whl (63 kB)
Collecting MarkupSafe>=2.0
  Using cached MarkupSafe-2.1.1-cp311-cp311-linux_x86_64.whl
Collecting python-dateutil
  Using cached python_dateutil-2.8.2-py2.py3-none-any.whl (247 kB)
Collecting charset-normalizer<3,>=2
  Using cached charset_normalizer-2.1.1-py3-none-any.whl (39 kB)
Collecting idna<4,>=2.5
  Using cached idna-3.4-py3-none-any.whl (61 kB)
Collecting urllib3<1.27,>=1.21.1
  Using cached urllib3-1.26.12-py2.py3-none-any.whl (140 kB)
Collecting certifi>=2017.4.17
  Using cached certifi-2022.9.24-py3-none-any.whl (161 kB)
Collecting smmap2>=2.0.0
  Using cached smmap2-3.0.1-py3-none-any.whl (1.1 kB)
Collecting six>=1.5
  Using cached six-1.16.0-py2.py3-none-any.whl (11 kB)
Collecting smmap>=3.0.1
  Using cached smmap-5.0.0-py3-none-any.whl (24 kB)
Installing collected packages: honcho, urllib3, smmap, six, semantic-version, MarkupSafe, idna, click, charset-normalizer, certifi, smmap2, requests, python-dateutil, jinja2, python-crontab, gitdb2, gitpython, frappe-bench
Successfully installed MarkupSafe-2.1.1 certifi-2022.9.24 charset-normalizer-2.1.1 click-8.1.3 frappe-bench-5.14.4 gitdb2-2.0.6 gitpython-2.1.15 honcho-1.1.0 idna-3.4 jinja2-3.0.3 python-crontab-2.6.0 python-dateutil-2.8.2 requests-2.28.1 semantic-version-2.8.5 six-1.16.0 smmap-5.0.0 smmap2-3.0.1 urllib3-1.26.12
$ pip list | grep bench                                                                   
frappe-bench       5.14.4
$ bench --help 
WARN: Command not being executed in bench directory
Usage:  [OPTIONS] COMMAND [ARGS]...

Options:
  --version
  --use-feature TEXT
  -v, --verbose
  --help              Show this message and exit.

Commands:
  backup-all-sites         Backup all sites in current bench
  config                   Change bench configuration
  disable-production       Disables production environment for the bench.
  download-translations    Download latest translations
  drop
  exclude-app              Exclude app from updating
  find                     Finds benches recursively from location
  get                      Clone an app from the internet or filesystem...
  get-app                  Clone an app from the internet or filesystem...
  include-app              Include app for updating
  init                     Initialize a new bench instance in the...
  install                  Install system dependencies for setting up...
  migrate-env              Migrate Virtual Environment to desired Python...
  new-app                  Create a new Frappe application under apps folder
  pip                      For pip help use `bench pip help [COMMAND]` or...
  remote-reset-url         Reset app remote url to frappe official
  remote-set-url           Set app remote url
  remote-urls              Show apps remote url
  remove                   Completely remove app from bench and re-build...
  remove-app               Completely remove app from bench and re-build...
  renew-lets-encrypt       Sets Up latest cron and Renew Let's Encrypt...
  restart                  Restart supervisor processes or systemd units
  retry-upgrade            Retry a failed upgrade
  rm                       Completely remove app from bench and re-build...
  set-mariadb-host         Set MariaDB host for bench
  set-nginx-port           Set NGINX port for site
  set-redis-cache-host     Set Redis cache host for bench
  set-redis-queue-host     Set Redis queue host for bench
  set-redis-socketio-host  Set Redis socketio host for bench
  set-ssl-certificate      Set SSL certificate path for site
  set-ssl-key              Set SSL certificate private key path for site
  set-url-root             Set URL root for site
  setup                    Setup command group for enabling setting up a...
  src                      Prints bench source folder path, which can be...
  start                    Start Frappe development processes
  switch-to-branch         Switch all apps to specified branch, or...
  switch-to-develop        Switch frappe and erpnext to develop branch
  update                   Performs an update operation on current bench.
$

Node.js

See this installation instructions. I use version 16.x.x (LTS version).

Yarn

After Node.js installation, you should have node and npm. Install Yarn using this command:



$ npm install -g yarn

Git

Usually all Linux distro has Git installed by default. Just in case your Linux box does not have Git or maybe you use MacOS or Windows, see installation instructions for Git.

Redis

Redis will be needed in bench directory initialization. Make sure that you have redis (or redis-stack) and redis --version has an output - for example:



$ redis-server --version
Redis server v=6.2.7 sha=00000000:0 malloc=jemalloc-5.1.0 bits=64 build=adcdff4a0d295794
$

Initialize `bench` Directory

Our applications will reside in one bench directory, therefore we need to initialize it first:



$ bench init --frappe-branch version-14 myERPNext14

Here's the screen dump:



$ bench init --frappe-branch version-14 myERPNext14 Setting Up Environment
$ python3 -m venv env
$ /home/bpdp/kerjaan/ptjim/erpnext/myERPNext14/env/bin/python -m pip install --quiet --upgrade pip
Getting frappe
$ git clone https://github.com/frappe/frappe.git --branch version-14 --depth 1 --origin upstream
Cloning into 'frappe'...
remote: Enumerating objects: 3162, done.
remote: Counting objects: 100% (3162/3162), done.
remote: Compressing objects: 100% (2836/2836), done.
remote: Total 3162 (delta 424), reused 1254 (delta 227), pack-reused 0
Receiving objects: 100% (3162/3162), 15.99 MiB | 1.76 MiB/s, done.
Resolving deltas: 100% (424/424), done.
Installing frappe
$ /home/bpdp/kerjaan/ptjim/erpnext/myERPNext14/env/bin/python -m pip install --quiet --upgrade -e /home/bpdp/kerjaan/ptjim/erpnext/myERPNext14/apps/frappe 
  DEPRECATION: zxcvbn-python is being installed using the legacy 'setup.py install' method, because it does not have a 'pyproject.toml' and the 'wheel' package is not installed. pip 23.1 will enforce this behaviour change. A possible replacement is to enable the '--use-pep517' option. Discussion can be found at https://github.com/pypa/pip/issues/8559
  DEPRECATION: PyQRCode is being installed using the legacy 'setup.py install' method, because it does not have a 'pyproject.toml' and the 'wheel' package is not installed. pip 23.1 will enforce this behaviour change. A possible replacement is to enable the '--use-pep517' option. Discussion can be found at https://github.com/pypa/pip/issues/8559
  DEPRECATION: docopt is being installed using the legacy 'setup.py install' method, because it does not have a 'pyproject.toml' and the 'wheel' package is not installed. pip 23.1 will enforce this behaviour change. A possible replacement is to enable the '--use-pep517' option. Discussion can be found at https://github.com/pypa/pip/issues/8559
  DEPRECATION: traceback-with-variables is being installed using the legacy 'setup.py install' method, because it does not have a 'pyproject.toml' and the 'wheel' package is not installed. pip 23.1 will enforce this behaviour change. A possible replacement is to enable the '--use-pep517' option. Discussion can be found at https://github.com/pypa/pip/issues/8559
  DEPRECATION: maxminddb is being installed using the legacy 'setup.py install' method, because it does not have a 'pyproject.toml' and the 'wheel' package is not installed. pip 23.1 will enforce this behaviour change. A possible replacement is to enable the '--use-pep517' option. Discussion can be found at https://github.com/pypa/pip/issues/8559
  DEPRECATION: hiredis is being installed using the legacy 'setup.py install' method, because it does not have a 'pyproject.toml' and the 'wheel' package is not installed. pip 23.1 will enforce this behaviour change. A possible replacement is to enable the '--use-pep517' option. Discussion can be found at https://github.com/pypa/pip/issues/8559
  DEPRECATION: maxminddb-geolite2 is being installed using the legacy 'setup.py install' method, because it does not have a 'pyproject.toml' and the 'wheel' package is not installed. pip 23.1 will enforce this behaviour change. A possible replacement is to enable the '--use-pep517' option. Discussion can be found at https://github.com/pypa/pip/issues/8559
  DEPRECATION: rauth is being installed using the legacy 'setup.py install' method, because it does not have a 'pyproject.toml' and the 'wheel' package is not installed. pip 23.1 will enforce this behaviour change. A possible replacement is to enable the '--use-pep517' option. Discussion can be found at https://github.com/pypa/pip/issues/8559
  DEPRECATION: premailer is being installed using the legacy 'setup.py install' method, because it does not have a 'pyproject.toml' and the 'wheel' package is not installed. pip 23.1 will enforce this behaviour change. A possible replacement is to enable the '--use-pep517' option. Discussion can be found at https://github.com/pypa/pip/issues/8559
  DEPRECATION: googlemaps is being installed using the legacy 'setup.py install' method, because it does not have a 'pyproject.toml' and the 'wheel' package is not installed. pip 23.1 will enforce this behaviour change. A possible replacement is to enable the '--use-pep517' option. Discussion can be found at https://github.com/pypa/pip/issues/8559
  DEPRECATION: cairocffi is being installed using the legacy 'setup.py install' method, because it does not have a 'pyproject.toml' and the 'wheel' package is not installed. pip 23.1 will enforce this behaviour change. A possible replacement is to enable the '--use-pep517' option. Discussion can be found at https://github.com/pypa/pip/issues/8559
$ yarn install
yarn install v1.22.19
warning ../../../../../../package.json: No license field
[1/5] Validating package.json...
[2/5] Resolving packages...
[3/5] Fetching packages...
[4/5] Linking dependencies...
warning " > @frappe/esbuild-plugin-postcss2@0.1.3" has unmet peer dependency "less@^4.x".
warning " > @frappe/esbuild-plugin-postcss2@0.1.3" has unmet peer dependency "stylus@^0.x".
warning Workspaces can only be enabled in private projects.
[5/5] Building fresh packages...
Done in 237.62s.
Found existing apps updating states...
$ bench build
Assets for Release v14.16.0 don't exist
✔ Application Assets Linked                                                                                                                          


yarn run v1.22.19
warning ../../../../../../package.json: No license field
$ node esbuild --production --run-build-command
clean: postcss.plugin was deprecated. Migration guide:
https://evilmartians.com/chronicles/postcss-8-plugin-migration
clean: postcss.plugin was deprecated. Migration guide:
https://evilmartians.com/chronicles/postcss-8-plugin-migration
clean: postcss.plugin was deprecated. Migration guide:
https://evilmartians.com/chronicles/postcss-8-plugin-migration
clean: postcss.plugin was deprecated. Migration guide:
https://evilmartians.com/chronicles/postcss-8-plugin-migration
Browserslist: caniuse-lite is outdated. Please run:
  npx browserslist@latest --update-db
  Why you should do it regularly: https://github.com/browserslist/browserslist#browsers-data-updating
File                                                        Size

frappe/dist/js/
├─ bootstrap-4-web.bundle.22U72DEL.js                       1.73 Kb
├─ controls.bundle.XMXXTEDE.js                              1226.29 Kb
├─ data_import_tools.bundle.ZHGGYJ52.js                     106.10 Kb
├─ desk.bundle.MLU24LZA.js                                  1315.72 Kb
├─ dialog.bundle.IBOC573P.js                                52.67 Kb
├─ form.bundle.DM6ACTZY.js                                  153.74 Kb
├─ frappe-web.bundle.UEU5WTAG.js                            823.04 Kb
├─ libs.bundle.YZMCKPNH.js                                  574.13 Kb
├─ list.bundle.TT33PVXT.js                                  185.23 Kb
├─ logtypes.bundle.7STJ7YLS.js                              0.73 Kb
├─ recorder.bundle.5AOEUOFD.js                              179.54 Kb
├─ report.bundle.GFUQKB7W.js                                170.93 Kb
├─ user_profile_controller.bundle.YR6XHZRM.js               11.35 Kb
├─ video_player.bundle.UO3KNN5D.js                          120.59 Kb
├─ web_form.bundle.KZ3DGEKH.js                              1560.14 Kb
├─ print_format_builder.bundle.KP4FAW42.js                  170.39 Kb
├─ build_events.bundle.L2HAVD4K.js                          11.62 Kb
└─ kanban_board.bundle.VCVKXCPT.js                          27.42 Kb

frappe/dist/css/
├─ desk.bundle.ZJ65KRGK.css                                 542.84 Kb
├─ email.bundle.2SCQFONP.css                                4.02 Kb
├─ login.bundle.YF3JSIEM.css                                23.56 Kb
├─ print.bundle.4DZBYDHD.css                                194.76 Kb
├─ print_format.bundle.P4TGM3H5.css                         177.61 Kb
├─ report.bundle.INQWGNNN.css                               5.36 Kb
├─ web_form.bundle.ICCT62YT.css                             14.73 Kb
└─ website.bundle.DQ2V2XQ5.css                              420.08 Kb

frappe/dist/css-rtl/
├─ desk.bundle.2VE3L2MS.css                                 543.10 Kb
├─ email.bundle.5KSKAB3K.css                                4.02 Kb
├─ login.bundle.BI7G5G42.css                                23.56 Kb
├─ print.bundle.3YGOKYDF.css                                194.91 Kb
├─ print_format.bundle.N76YW3PD.css                         177.72 Kb
├─ report.bundle.S5GOBZKX.css                               5.35 Kb
├─ web_form.bundle.KPBAPSVI.css                             14.72 Kb
└─ website.bundle.MQZU7APE.css                              420.24 Kb

 DONE  Total Build Time: 12.268s

 WARN  Cannot connect to redis_cache to update assets_json
 WARN  Cannot connect to redis_cache to update assets_json
 WARN  Cannot connect to redis_cache to update assets_json
Done in 15.86s.
SUCCESS: Bench myERPNext14 initialized
$

At this point, we already have one bench directory, named myERPNext14.

NOTE: The term bench/Bench usually denotes two things: directory and CLI. Starting now, we will call bench/Bench directory as bench/Bench and bench/Bench CLI as bench/Bench CLI.

In this bench, we will create our site and then get the app (ERPNext) and install our ERPNext app into our site.

Create New Site

Set the host first:



$ cat /etc/hosts
127.0.0.1   localhost
127.0.1.1   dellvuan    dellvuan
127.0.1.1   myerpnext   myerpnext

# The following lines are desirable for IPv6 capable hosts
::1     localhost ip6-localhost ip6-loopback
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
$ ping myerpnext
PING myerpnext (127.0.1.1) 56(84) bytes of data.
64 bytes from dellvuan (127.0.1.1): icmp_seq=1 ttl=64 time=0.052 ms
64 bytes from dellvuan (127.0.1.1): icmp_seq=2 ttl=64 time=0.031 ms
^C
--- myerpnext ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1021ms
rtt min/avg/max/mdev = 0.031/0.041/0.052/0.010 ms
$

Enter the directory which we have created before using bench init (myERPNext14) and then use this command to create a new site (myerpnext01):



$ bench new-site --db-name myerpnextdb01 myerpnext01 
MySQL root password: 

Installing frappe...
Updating DocTypes for frappe        : [========================================] 100%
Updating country info               : [========================================] 100%
Set Administrator password: 
Re-enter Administrator password: 
Updating Dashboard for frappe
myerpnext01: SystemSettings.enable_scheduler is UNSET
*** Scheduler is disabled ***
$

If we do not use --db-name then bench CLI will use randomly generated name. We need to answer Administrator password. Take note of the password, we're gonna need this later.

Get ERPNext Application

Use this command:



$ bench get-app --branch version-14 erpnext

Here's the screendump:



$ bench get-app --branch version-14 erpnext
Getting erpnext
$ git clone https://github.com/frappe/erpnext.git --branch version-14 --depth 1 --origin upstream
Cloning into 'erpnext'...
remote: Enumerating objects: 4909, done.
remote: Counting objects: 100% (4909/4909), done.
remote: Compressing objects: 100% (4172/4172), done.
remote: Total 4909 (delta 971), reused 2275 (delta 506), pack-reused 0
Receiving objects: 100% (4909/4909), 17.18 MiB | 1.72 MiB/s, done.
Resolving deltas: 100% (971/971), done.
Ignoring dependencies of erpnext. To install dependencies use --resolve-deps
Installing erpnext
$ /home/bpdp/kerjaan/ptjim/erpnext/myERPNext14/env/bin/python -m pip install --quiet --upgrade -e /home/bpdp/kerjaan/ptjim/erpnext/myERPNext14/apps/erpnext 
  DEPRECATION: pycountry is being installed using the legacy 'setup.py install' method, because it does not have a 'pyproject.toml' and the 'wheel' package is not installed. pip 23.1 will enforce this behaviour change. A possible replacement is to enable the '--use-pep517' option. Discussion can be found at https://github.com/pypa/pip/issues/8559
  DEPRECATION: jsonobject is being installed using the legacy 'setup.py install' method, because it does not have a 'pyproject.toml' and the 'wheel' package is not installed. pip 23.1 will enforce this behaviour change. A possible replacement is to enable the '--use-pep517' option. Discussion can be found at https://github.com/pypa/pip/issues/8559
  DEPRECATION: taxjar is being installed using the legacy 'setup.py install' method, because it does not have a 'pyproject.toml' and the 'wheel' package is not installed. pip 23.1 will enforce this behaviour change. A possible replacement is to enable the '--use-pep517' option. Discussion can be found at https://github.com/pypa/pip/issues/8559
  DEPRECATION: plaid-python is being installed using the legacy 'setup.py install' method, because it does not have a 'pyproject.toml' and the 'wheel' package is not installed. pip 23.1 will enforce this behaviour change. A possible replacement is to enable the '--use-pep517' option. Discussion can be found at https://github.com/pypa/pip/issues/8559
  DEPRECATION: gocardless-pro is being installed using the legacy 'setup.py install' method, because it does not have a 'pyproject.toml' and the 'wheel' package is not installed. pip 23.1 will enforce this behaviour change. A possible replacement is to enable the '--use-pep517' option. Discussion can be found at https://github.com/pypa/pip/issues/8559
$ yarn install
yarn install v1.22.19
warning ../../../../../../package.json: No license field
[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
[4/4] Building fresh packages...
Done in 1.31s.
$ bench build --app erpnext
✔ Application Assets Linked                                                                                                                          


yarn run v1.22.19
warning ../../../../../../package.json: No license field
$ node esbuild --production --apps erpnext --run-build-command
clean: postcss.plugin was deprecated. Migration guide:
https://evilmartians.com/chronicles/postcss-8-plugin-migration
clean: postcss.plugin was deprecated. Migration guide:
https://evilmartians.com/chronicles/postcss-8-plugin-migration
clean: postcss.plugin was deprecated. Migration guide:
https://evilmartians.com/chronicles/postcss-8-plugin-migration
clean: postcss.plugin was deprecated. Migration guide:
https://evilmartians.com/chronicles/postcss-8-plugin-migration
Browserslist: caniuse-lite is outdated. Please run:
  npx browserslist@latest --update-db
  Why you should do it regularly: https://github.com/browserslist/browserslist#browsers-data-updating
File                                                        Size

erpnext/dist/js/
├─ bank-reconciliation-tool.bundle.M2IJU46J.js              15.49 Kb
├─ erpnext-web.bundle.SJSJGLAQ.js                           33.34 Kb
├─ erpnext.bundle.N434KUXQ.js                               171.45 Kb
├─ hierarchy-chart.bundle.7XNMCT5W.js                       197.67 Kb
├─ item-dashboard.bundle.FDBNNRVN.js                        10.01 Kb
└─ point-of-sale.bundle.6IPZTPSS.js                         92.75 Kb

erpnext/dist/css/
├─ erpnext-web.bundle.A6SQ2ID7.css                          25.63 Kb
├─ erpnext.bundle.U356GCQU.css                              45.08 Kb
└─ erpnext_email.bundle.IZ3Q7O74.css                        0.56 Kb

erpnext/dist/css-rtl/
├─ erpnext-web.bundle.V7HAL4NV.css                          25.62 Kb
├─ erpnext.bundle.VJVO6DLO.css                              45.07 Kb
└─ erpnext_email.bundle.5XL2M5KG.css                        0.56 Kb

 DONE  Total Build Time: 1.609s

 WARN  Cannot connect to redis_cache to update assets_json
 WARN  Cannot connect to redis_cache to update assets_json
 WARN  Cannot connect to redis_cache to update assets_json
Done in 5.35s.
$

Install ERPNext Into the Site

Once we get ERPNext, we can install it into our site. In version 14, we need to install payments app first (see https://discuss.erpnext.com/t/getting-error-when-running-install-app-erpnext/92832):



$ bench get-app payments
Getting payments
$ git clone https://github.com/frappe/payments.git  --depth 1 --origin upstream
Cloning into 'payments'...
remote: Enumerating objects: 84, done.
remote: Counting objects: 100% (84/84), done.
remote: Compressing objects: 100% (74/74), done.
remote: Total 84 (delta 12), reused 37 (delta 4), pack-reused 0
Receiving objects: 100% (84/84), 41.23 KiB | 1.72 MiB/s, done.
Resolving deltas: 100% (12/12), done.
Ignoring dependencies of payments. To install dependencies use --resolve-deps
Installing payments
$ /home/bpdp/kerjaan/ptjim/erpnext/myERPNext14/env/bin/python -m pip install --quiet --upgrade -e /home/bpdp/kerjaan/ptjim/erpnext/myERPNext14/apps/payments 
  DEPRECATION: paytmchecksum is being installed using the legacy 'setup.py install' method, because it does not have a 'pyproject.toml' and the 'wheel' package is not installed. pip 23.1 will enforce this behaviour change. A possible replacement is to enable the '--use-pep517' option. Discussion can be found at https://github.com/pypa/pip/issues/8559
$ bench build --app payments
✔ Application Assets Linked                                                                                                                          


yarn run v1.22.19
warning ../../../../../../package.json: No license field
$ node esbuild --production --apps payments --run-build-command
File                                                        Size

 DONE  Total Build Time: 399.758ms

clean: postcss.plugin was deprecated. Migration guide:
https://evilmartians.com/chronicles/postcss-8-plugin-migration
clean: postcss.plugin was deprecated. Migration guide:
https://evilmartians.com/chronicles/postcss-8-plugin-migration
clean: postcss.plugin was deprecated. Migration guide:
https://evilmartians.com/chronicles/postcss-8-plugin-migration
clean: postcss.plugin was deprecated. Migration guide:
https://evilmartians.com/chronicles/postcss-8-plugin-migration
 WARN  Cannot connect to redis_cache to update assets_json
 WARN  Cannot connect to redis_cache to update assets_json
 WARN  Cannot connect to redis_cache to update assets_json
Done in 3.92s.
$



$ bench --site myerpnext01 install-app erpnext
Installing payments...
Updating DocTypes for payments      : [========================================] 100%
* Installing Payment Custom Fields in Web Form
Updating Dashboard for payments

Installing erpnext...
Updating DocTypes for erpnext       : [========================================] 100%
Updating customizations for Address
Updating customizations for Contact
Updating Dashboard for erpnext
$

Setup Frappe for Production Environment

We can use bench CLI to setup Frappe for production environment, especially for specific user. Here, my username is bpdp, so we will do setup for user bpdp. To setup production environment using bench CLI, we need to use sudo since the command will change some system settings. Using sudo for miniconda distribution is a little bit tricky since sudo usually can not find command from miniconda because miniconda is installed for user. Therefore we need to use full path:



$ sudo /home/bpdp/software/python-dev-tools/miniconda39/envs/py310-erpnext/bin/bench setup production bpdp

At this point, our installation has fisnished successfully. Next, we will run our ERPNext app and doing some initial setup.

Run ERPNext

To run ERPNext, use bench CLI below;



$ bench start
...
...
<screendump>
...
...
16:31:26 web.1            |  * Running on http://0.0.0.0:8001/ (Press CTRL+C to quit)
...
...
16:31:56 watch.1          | Rebuilding bank-reconciliation-tool.min.js
16:31:56 watch.1          | Rebuilding erpnext.css
16:31:56 watch.1          | Rebuilding marketplace.css
16:31:56 watch.1          | Rebuilding erpnext-web.css
$

NOTE: The screendump above display the port which is accessible using browser where ERPNext serves.

Initial Setup

Using browser, access http://myerpnext:8001/, a login screen appear:

Use the password which has been created above and Administrator user.

Choose your language.

Choose region and fill timezone and currency.

Create user. You may put picture or not.

Choose domain / industry where our company operate. We may choose more than one for later process.

Brand of our company. Logo for our company also optional.

More info about our company can be filled now.

Wait until setup finish successfully.

Setup completed! Right now, we can start use our ERPNext. Enjoy!

Forem: Zimera Corporation

Bypass Transparent DNS Proxy

Getting Started with Redis and RedisGraph

Introduction

Redis Installation

RedisGraph

Installation

Configuration

Let's Try RedisGraph!

Belajar Rust - 03: IDE untuk Rust

Vim / Neovim

Instalasi Vim

Instalasi Neovim

Instalasi SpaceVim

Konfigurasi SpaceVim

Visual Studio Code / VSCodium

Instalasi VS Code / VSCodium

Extension untuk Rust

Eclipse

Managing a Software Development Team: Some Experiences

Introduction

Decide the tools which will be used by the team

Use a specific software development methodology, probably with some minor adaption

Make some conventions regarding technical issues

Enforce Programming Idiom

Know the client(s) and their problems which are tried to be solved

Decide the scope of the problems and insists on this.

Have a good interpersonal relationship and don’t be a jerk

Never let the team in a state of flux

Let the team concentrate on technical matters

Let the team member knows each other about progress and difficulties

Inform the team about your progress too

Communicate. Communicate. Communicate

Always keep backup of everything

Use Version Control System

Use web based bug tracking system, project management software, and/or wiki

Belajar Rust - 02: Instalasi Rust

Rilis Rust

Siklus Rilis Rust

Edisi Rust

Rust Playground

Instalasi Rust

Uninstall Rust

Memperbarui Rust

Plugin untuk subcommand Cargo

Instalasi Plugin

Memahami Ekosistem Rust

Pustaka Rust

Pengenalan Cargo

Inisialisasi Proyek

Struktur Direktori dan Aplikasi Proyek Rust

Membangun Proyek

Menjalankan Hasil

Menggunakan cargo untuk Mengelola Dependencies

Membersihkan Hasil Kompilasi

Clippy

Mengikuti Perkembangan Rust

Belajar Rust - 01: Mengenal Bahasa Pemrograman Rust

Apakah Rust Itu?

Sejarah Singkat Rust

Paradigma Pemrograman Rust

Lisensi Rust

Software yang Dibangun Menggunakan Rust

Domain Masalah dari Rust

Using YugabyteDB in Python App Development

Install and Configure YugabyteDB

Data Preparation

SQL Data

NOSQL Column-wide Data - Apache Cassandra

Python - Drivers

Let's Code!

Accessing SQL Data

Accessing Cassandra Data Model

WebSharper: Getting Started Easily

Install Application Template

Update Templates

Multiple .NET SDKs and Runtimes Installation

Install LTS Version First

Install Current Version

Install versi beta / RC

Plugin untuk subcommand `Cargo`

Menggunakan `cargo` untuk Mengelola Dependencies

Initialize `bench` Directory