#Bitnami
Tumblr posts tagged #Bitnami from across Tumblr — no login required.
Migrating My WordPress Database from a Lightsail Instance to a Standalone Database Last year, I moved this blog off of a EC2 instance running a too-old version of PHP to a Lightsail instance. I had to restart that instance in order to retrieve the images associated with all the prior posts so they looked exactly as they did before, but the end result was the same blog at a lower monthly cost. Since then, I installed and configured the WP Offload Media Lite plug-in to push all… View On WordPress
Https Optimization for your WordPress Website
Https Optimization for your WordPress Website So you read my earlier post about installing SSL certificate for your WordPress website. If not read from here . So after installing SSL certificate, you may experience some issues such as content duplication issue, https not working for some pages, the site still prefers the non-secure version. etc, Well, I am here to help you with all these pesky issues. so let’s begin. My Server Configuration View On WordPress
Senior Kubernetes Engineer at Bitnami
Senior Kubernetes Engineer at Bitnami Senior Kubernetes Engineer at Bitnami Bitnami is on a mission to bring awesome applications on every platform to everyone. We’re looking for an experienced Senior Engineer to lead development of some of the most exciting open source Kubernetes-related tools being developed today. You will be working alongside developers who, prior to Bitnami, had been building critical infrastructure software at… View On WordPress
bitnamiで簡単にMacのローカル環境へWordPressを設置する方法 AMP対応のWordPress構築に興味が湧いてきたのでWordPressブログテーマ構築を久しぶりに始めました。 普段はランディングページのデザインとコーディングの案件ばかり受けているためWordPressに関してはテーマ作成程度の知識しかありません。 私の場合はWordPressは趣味の範囲で楽しむ程度に使っています。 私はMacを使っているのでbitnamiというWordPressをインストールできるツールを使ってローカル環境へWordPressサイトを作りました。 PCにテーマやプラグインのデータがあるとバックアップにもなるので、必ず新しいWordPressサイトを作る時はローカル環境から作ります。 （１）bitnamiのサイトへ行きMac用のインストーラをダウンロードします。 https://bitnami.com/stack/wordpress （２）インストーラをクリックして開きます。 （３）言語は日本語がないので「English」を選びます。 （４）セットアップ画面が開きます。「Next」をクリックします。 （５）インストールするフォルダはデフォルトのままで「Next」をクリックします。 （６）WordPressを設置するフォルダを選びます。 初期のままでも問題ないので「Next」をクリックします。 （７）アカウント設定をします。 名前、ログイン、パスワードを任意のものに変えて設定します。 ログイン名を初期設定の「User」のままにして、次へ進むとエラーみたいになりました。 そのため「admin」に変更しました。 本番サーバーではセキュリティの安全のために変更しようと思います。 （予測されやすい「admin」はWordPressでは絶対ダメです） （８）ブログ名を決めて入力します。 後で変更可能なので私はデフォルトのままにして「Next」へ進みました。 SMTPの設定です。 ローカルでテーマ制作する場合には必要ないと思ったので私は省いて「Next」へ進みました。 必要な場合はSMTPの設定します。 （９）途中、クラウドの設定もありますがここでは省きました。 インストールするかどうか聞かれるので「Next」へ進みます。 インストールが始まるのでしばらく待ちます。 （１０）最後は「Finish」でインストールが完了します。 （１１）下記のページがブラウザで表示されます。 下記のURLでWordPressサイトへアクセスできます。 初期のWordPressアドレス http://127.0.0.1:8080/wordpress/ 管理画面アドレス http://127.0.0.1:8080/wordpress/wp-admin bitnamiのWordPressを日本語化する方法 （１）「Settings」→「General」を選択します。 （２）「Site Language」を「日本語」に選択し「Save Changes」をクリックするとWordPressが日本語化されます。 bitnamiはデフォルトで以下のプラグインが入っています。 「All In One SEO Pack」と「JetPack」はよく入れるので助かるかなと個人的には思いました。 「VersionPress」って知らないから何かな？と思ったらWordPressをGitのバージョン管理してくれるプラグインのようです。 「WP-Mail-SMTP」はSMTPサーバを使ってメールを送信できるようにするプラグインでContact Form 7の補助的なプラグインのようです。 ▼参考になったサイト PCにWordPressローカル環境を「Bitnami」で作成する方法 https://nelog.jp/how-to-install-bitnami Contact Form 7プラグインでGmailのSMTPサーバを使ってメール送信 https://www.adminweb.jp/wordpress-plugin/list/index12.html ▼WordPressテーマ構築の参考になりそうな書籍 WordPress AMP対応 モダンWeb制作 レッスンブック posted with カエレバ エビスコム ソシム 2017-01-24 Amazon WordPressデザインブック HTML5&CSS3準拠 (WordPress DESIGN BOOK) posted with カエレバ エビスコム ソシム 2015-09-11 Amazon
How to Install AWS Lightsail WordPress
work to be done in advance Sign up for AWS and sign up for Lightsail Introduction If you’re looking to create a website or a blog using WordPress, AWS Lightsail provides a quick and easy way to set up your own virtual private server (VPS) with minimal effort. In this article, we will guide you through the step-by-step process of installing AWS Lightsail WordPress. By the end of this tutorial, you’ll have your WordPress website up and running on the AWS Lightsail platform. 1. Create *Instance First, you need to create an instance like the screen. For the platform, select Linux/Unix environment. The reason for this is that there are more blueprints and, in practice, Linux is easier to manage servers. And for Blueprint, let’s choose WordPress. *(AWS) What is an instance? An AWS instance is a cloud computing resource provided by Amazon Web Services (AWS). Instances are virtual servers that provide a computing environment in which you can run multiple operating systems (OS) and software. AWS instances come in a variety of sizes and performance options, and you can choose an instance type to suit your needs. For example, a small instance may be sufficient to host a basic web server, but larger and more powerful instances may be needed to run large databases or complex applications. You can create and launch as many AWS instances as you need on demand, and you can configure instance types, operating systems, storage and networking options, and more. Users can also scale their applications by resizing instances or using multiple instances as needed. AWS instances offer the flexibility and scalability of cloud computing, and you use and pay for as many resources as you need. This reduces the burden of managing infrastructure and allows you to quickly deploy and scale applications. *(IT) What is Blue Print? An IT blueprint is a plan or design document for implementing an information technology (IT) system or solution. When starting an IT project, a business or organization must consider various factors such as overall system architecture, network configuration, hardware and software requirements, security policies, database structure, and more. An IT blueprint documents these elements in detail and provides them as a blueprint that can be used during the implementation and maintenance phases. 2. Connect SSH to the created instance AWS Lightsail Dashboard Instances Instance is created after time passes as shown in the screen. *Click the SSH connection button to open the Lightsail Terminal (input window). ssh connection *What is SSH SSH stands for “Secure Shell,” and is a protocol that allows you to remotely access and communicate with a computer securely over a network. SSH uses encryption technology to ensure data confidentiality and integrity and provides secure access through authentication and encryption. SSH allows you to securely log in and run commands on another computer over the Internet or a local network. With SSH, you can authenticate by entering a password, or you can connect using a public/private key pair. SSH uses TCP port 22 by default, and most operating systems support SSH client and server software. SSH is used for a variety of purposes, such as remotely managing servers or transferring files. In a web hosting service, you can connect to a web server through SSH and perform tasks such as uploading files or changing settings. In addition, you can remotely connect to the server to execute commands or download files. Because SSH uses encryption technology, data transmitted over the network is safely protected to prevent leakage of important information. Then, a window appears as shown in the screen below. The important point here is that you need to enter the following command, the reason is to know the ID and password of WordPress. less bitnami_credentials lightsail ssh 3. Visit with Public IP public IP If you enter Public IP (a kind of phone book on the Internet = IP address) in the URL window, you can check the created template. If you add /admin to the address, you can check the login screen. If you enter the ID and password you found above, you can check the WordPress admin screen. example - 18.15.XXX.XX/admin WordPress login screen WordPress admin screen 4. How to change WordPress User password WordPress password If you want to change the password, click the Users menu on the left side of the administrator screen, and then click the Edit user button to change information such as the password. Read the full article
Bootstrap Multisite Wordpress on AWS Lightsail
Bootstrap Multisite WordPress on AWS Lightsail I wrote one on how to do this with Digital Ocean Multisite WordPress , but if you are on AWS, then you have some different options for Lightsail which is the easiest option. The instructions are really confusing, but basically, you use the Lightsail instructions to get it running and to get Route53 configured and then the Bitnami Multisite WordPress instructions to configure it. Those instructions… View On WordPress
Secure your Website with Let's Encrypt free SSL
Secure your Website with Let’s Encrypt free SSL The first question anyone asks when we talk about SSL is Why should I use SSL/TLS? Think about it like this, what will happen if you send a letter through the traditional post without sealing the envelope. Well, some gentlemen will just ignore, some curious person may take a peek inside. But what if he is a malicious person? what if he misuses the information he got from the letter. You are in… View On WordPress
Mudah Mengatur Permission di Bitnami XAMPP di GNU/Linux
Mudah Mengatur Permission di Bitnami XAMPP di GNU/Linux Adanya XAMPP sejak awal memang diperuntukan tuk mempermudah web developer, satu aplikasi berisi semua paket yang dibutuhkan web developing, yakni Apache, MySQL/MariadDB, PHP dan Perl sesuai singkatanya XAMPP. Sering kali saya mendapati suatu pertanyaan kepada mereka yang baru pertama kali mencoba atau migrasi sistem operasi dari Windows ke GNU/Linux, mengenai XAMPP yang terkendala pada saat… View On WordPress
Battle: Bitnami VMs vs Jidoteki VMs
[ author: Alex ] I discovered Bitnami a while back, but never took the time to try out their virtual appliances. I recently stumbled on them again and decided to open up the Bitnami ownCloud virtual appliance, to compare it with a Jidoteki ownCloud virtual appliance I created just for testing. Here’s our post about a RPi ownCloud we built a while back. It’s almost identical to the x86_64 version. Comparing the VMs 1. The first thing I noticed were the file sizes: Bitnami: 448MB compressed, 1.5GB uncompressed (on disk) Jidoteki: 90MB compressed, 141MB uncompressed (on disk) That’s a 10x difference in disk usage for a VM that does the exact same thing. 2. Something interesting about the disks: Bitnami: 1 x 17GB disk (sda1) w/ext4 Jidoteki: 1 x 8GB disk (sda1) w/ext2, 1 x 250GB disk (sdb1) w/ext4 + LVM I thought this Bitnami disk setup was weird, since ownCloud can easily require a lot of disk space for storing its data - why doesn’t the the VM ship with a 2nd disk by default? Jidoteki includes a 2nd disk setup with LVM, and automatically expands on boot when the user attaches a 3rd, 4th, 5th, or even 6th disk. Of course that is entirely configurable. 3. Network adapters Bitnami: PCNet32 (AMD PCnet-PCI II) in Bridged mode Jidoteki: E1000 (Intel Pro/1000 MT Desktop) in NAT mode I guess this doesn’t matter so much, since the user can change it themselves, but the pcnet32 adapter is a 10mbit adapter , compared with the e1000 which is 1gbit . Bridged mode by default will automatically make the VM accessible on the local network - before it has a chance to be configured. I think that’s a security risk, albeit a rather small one, at the expense of convenience - which is something I usually frown upon. We set ours to NAT by default, which limits access to the user’s local computer - default “secured” (I know, I know, NAT is not security..). 4. VM import and boot times were also quite interesting: Bitnami: 5mins import, 5mins boot Jidoteki: 30seconds import, 30seconds boot Import and boot were done with VirtualBox on my MacBook Air. Both will likely be much faster using VMware, or a faster computer. I’m not sure what the Bitnami appliance was doing behind the scenes during the boot process, since all output is suppressed early in the boot process. Verdict: Jidoteki VMs are better Ideas for Bitnami: 1) There is almost no output from the moment it boots until the login screen with the Bitnami banner. This made me question whether the boot was working or not. 2) The WRITE SAME error message is common for virtual machine disks. It’s not harmful, but scary. We suppress it with this code early in the boot process: ( See Gist on GitHub ) # Suppress WRITE SAME messages disks=`find /sys | grep max_write_same_blocks` for i in $disks; do [ -f “$i” ] && echo 0 > “$i” done 3) Replace GRUB with Syslinux for faster boot. 4) Setup LVM by default, so the disk can be expanded in the future. LVM root is sometimes challenging, and quite difficult to recover, so perhaps follow our approach instead ;) Comparing the VM contents To compare the contents, I mounted the VMDK disk on a Linux system with the help of qemu-nbd . 1. Too many files Bitnami: 67123 files and directories Jidoteki: 11 files and directories No wonder the Bitnami OVA is so big, it has way too much stuff! ;) Haha ok, so we cheated here. In fact the rootfs on the Jidoteki OVA contains compressed squashfs packages (TCZ extensions) which hold all the files for specific applications. This follows the TinyCore Linux architecture, which allows us to have only a few files on disk representing the entire OS, libraries and applications. 2. Open Source licenses Bitnami: 77 files found in /opt/bitnami/licenses/, 0 NOTICE file Jidoteki: 8 files found in /usr/share/doc/License/, 1 NOTICE file Bitnami does a remarkable job of including all licenses for every Open Source software used in the appliance. Unfortunately, there’s no indication on where to obtain the sources . For the record, that’s not good enough for GPL compliance , and it’s useless for people who want to modify the software or to see what patches were applied. The Jidoteki appliances include a NOTICE file in the License directory, with a URL to download all the individual sources , patches, and build scripts, as well as an ISO containing all the sources. Only the GPL requires that, but we do it for all the Open Source software we include. 3. Namespacing and separation Bitnami: All changes namespaced to /opt/bitnami Jidoteki: All changes namespaced to /opt/jidoteki, except some things Jidoteki scatters OS customizations all over the place and it’s a bit of a mess, but there’s one important difference: All OS customizations are contained in the rootfs . The base OS (corepure64) is completely unmodified except for the kernel modules which were updated. This is quite different from Bitnami, which is a full OS installation. That means on the Bitnami appliance it’s impossible to determine what parts of the OS were customized, and what shipped by default with the OS. 4. OS File and directory sizes Bitnami: ~800MB full OS, full documentation, full kernel modules and headers, unstripped binaries, perl and python libs (probably required for Ubuntu). Jidoteki: ~12MB bare minimum OS, no documentation, optimized VM kernel modules, no headers, stripped binaries, no perl or python libriaries. The OS used in Jidoteki appliances ( TinyCore Linux for now…) is ridiculously small and lightweight. They made a great effort to cut out the cruft and leave us with a fully functioning system. The Bitnami OS seems to be completely un-optimized and accounts for half the disk space used in the appliance. That becomes an issue when you want to run multiple appliances side-by-side. 5. App Files and directory sizes Bitnami: ~636MB for Bitnami, the ownCloud app, and its dependencies Jidoteki: ~125MB for Jidoteki, the ownCloud app, and its dependencies Bitnami does something interesting here: they include a common directory of shared libraries, locales, and other files which use up 100MB, and which are already included with the OS . It seems they duplicated those files to maintain control of shared libraries independently of the base OS. They also include the full Apache and PHP applications, which also use nearly 100MB. Jidoteki includes a stripped down version of Nginx and PHP instead, which only require 8MB. Verdict: Jidoteki VMs are better Ideas for Bitnami: 1) Put more effort into trimming down the base OS. All those libraries and binaries are typically not needed, or are only needed for one specific system. Ideally, you could switch to a smaller base OS which already has everything stripped down - but that’s a lot of work. It’s typically easier to refactor than rewrite ;) 2) Consider open sourcing and distributing the actual sources of your appliances, and separating the Bitnami-specific files from the default Ubuntu files. I understand they are probably all just unmodified base files/packages from Ubuntu, but that doesn’t help me know what changed in the OS you provided. Comparing security and updates It seems Bitnami does a great job of keeping on top of security issues. Their changelogs appear to be automatically generated, but they are frequent and quite well up-to-date, so that’s good. 1. Updates to the base OS Bitnami: looks like a simple apt-get upgrade combined with a Bitnami-specific upgrade process Jidoteki: Jidoteki-specific offline upgrade process The Bitnami upgrade process seems quite simple, but a lot is left in the hands of the user. The appliance itself must be maintained by the user, requires internet for updates, and can disrupt ownCloud if something breaks. With Jidoteki, we handle the maintenance of the entire OS, along with kernel and CVE security updates. A user only needs to upload our update package to the appliance, and it will automatically update the files on the boot disk. The process is atomic and almost guaranteed to work. A reboot is required to boot the OVA with the latest version. 2. Updates to ownCloud Bitnami: lots of manual steps and DB migration stuff (occ upgrade) Jidoteki: automatic with auto occ upgrade on reboot We automated the entire ownCloud app upgrade process, including the DB migrations. This was necessary because ownCloud does things a bit differently. Bitnami leaves it to you with a set of outdated instructions to follow. Fingers crossed if you’re successful on the first try ;) 3. Internet updates Bitnami: yes Jidoteki: no We aim for our appliances to run behind the firewall, and in fact they don’t even require internet at all. You can literally plug in a USB key with an update package, and then use that to perform an upgrade of a Jidoteki appliance. Of course we have a method of performing online internet updates as well, but that’s not the default. Bitnami defaults to online/internet updates because it’s more convenient. Again I think that’s not the best approach, but probably necessary considering their market. 4. “The user can fudge the appliance factor” Bitnami: oh yes Jidoteki: nope With Bitnami, the user has full root access to the appliance, and can pretty much do anything - including break it. Sure it’s the user’s fault if they do, but it significantly increases their support workload from people who have no idea what they’re doing. Jidoteki targets enterprise installations. We make sure to run the OS in memory only, and to have a read-only system to prevent “accidental” changes. This is by design in TinyCore Linux, which is another reason we use that as the base OS. Verdict: Jidoteki VMs are better Ideas for Bitnami: 1) Consider a read-only OS to prevent users from making unexpected changes. Some parts of the system can be read/write, but that should be reserved for configuration files and “data”, not libraries and binaries. If someone wants to install their own version of Apache, they should do it on their own Linux installation. 2) When updates are not atomic, bad things can happen . It seems like a repeat of the previous point, but if the user makes a small system change, and applies an update that fails, they could lose all their data - which is a terrible situation. Comparing system management This is the last point, thanks for sticking through to the end. 1. Network settings management through the console Bitnami: login as bitnami, you’re on your own Jidoteki: console gui to configure basic network settings When people first boot an appliance, the first thing they will need to do is configure the network settings, perhaps either change the IP or specify different DNS servers. Jidoteki appliances always have a simple console boot gui to change those settings - which doesn’t require a login or typing obscure commands. 2. App and other settings management Bitnami: login as bitnami, use ctlscript.sh or other obscure commands Jidoteki: web Dashboard and REST API for system management, or obscure commands haha Bitnami appliances don’t include a Management Dashboard, which is unfortunate. They do provide phpMyAdmin and SSH, but everything else seems to be command-line based. Jidoteki includes a user-friendly web D ashboard and a dev-friendly REST API for system management. It’s a bit limited in what it can do, but the basics are there (seeing service status, appliance usage graphs, etc). It’s sufficient for a first-run and for basic maintenance. Verdict: Well you’ve probably figured it out by now Conclusion I didn’t mean this post to knock on Bitnami. Their company seems like it has a really great culture, and I love that they are supporting Open Source and simplifying access to Open Source Software. Their contributions have been valuable so far, but they need to improve in certain areas regarding their virtual machines. Jidoteki is focused on creating rock-solid virtual appliances destined for the enterprise . We focus exclusively on doing things the correct way, with security and privacy as a top priority. Our solution is available for businesses who want to distribute their software on-premises using the best and simplest approach, along with the ability to automate appliance builds using continuous integration systems such as Jenkins. Feel free to contact us if you’re looking to build and distribute an on-prem virtual appliance. We’ll be more than happy to discuss your requirements.
Convert VMWare with vmkfstools -i failure...
I wanted to have a bitnami virtual appliance in my vSphere environment. Of course I was using the documentations and there was : If you want to run on VMware ESX or ESXi you can use the “vmkfstool” command line that you can find in your server host to import/export the machine: $ vmkfstools -i original.vmdk new.vmdk I tried it and I got : # vmkfstools -i bitnami-suitecrm-7.1.4-0-ubuntu-14.04.vmdk SuiteCRM.vmdk Failed to open ‘bitnami-suitecrm-7.1.4-0-ubuntu-14.04.vmdk’: The system cannot find the file specified (25). The file was there, but there was a failure. Google is your friend so I asked her and I found the solution ! # vmkload_mod multiextent Module multiextent loaded successfully And now I was able to use vmkfstools… Convert VMWare with vmkfstools -i failure… was originally published on blog.joostvandermade.com
라이트세일 인스턴스 업그레이드 및 설정 라이트세일 인스턴스 업그레이드 및 설정 월 5천원 정도 하던 국내 호스팅 서비스를 쓰다가, 저장 공간의 압박이 너무 커서 여기 저기로 옮겨 다니다 라이트세일에 정착한 것이 대략 2018년이다. (그 전에 해외 호스팅을 사용해봤는데, 얘들은 처음 1년 혹은 몇 달은 저렴하게 프로모션하지만, 그 이후로 요금은… 흠..) 처음 2년반 넘게 사용하는 동안에는 불편함이 없었는데, 워드프레스가 버전업이 되면서 무거워져서 그런지 점점 느려진다는 느낌이 들었다. 또, 번거롭게 설치하는 일 없이 사용하려고 bitnami 인스턴스를 사용했는데, 문제는 bitnami 스택에서 php만 업그레이드한다거나 하는 것이 어려웠다. (more…) View On WordPress
How to install wordpress locally without server
Looking for wordpress tutorial? Then here it is.Learn the first step of how to install wordpress locally without server using bitnami. If you are trying to code yourself for designing website.Then try this first step of installing software. Coding is not easy as you think.If you are using any other platforms then coding is easy.But for wordpress try using in-built themes and plugins for functionality. We will show you how to work on these items.Each will show you how to make your website more appealing and stylish. Bitnami is a software which has in-built sever with it.So only no need to install server. So make sure to learn this steps carefully.Lets start by how to install wordpress locally without server. Steps for installing wordpress locally without server First of all go to the browser and search for “bitnami wordpress”. Then select the first link (official website of bitnami). Click on the download for windows. Then select the operating system and click download. It will popup a form asking to signup.If you need you can signup else you can click no,thanks just download the software. Now open the software once it is downloaded. Click next until the blogs name and password page appears. There type your blogs name,password and then click next. Make sure to remember those credentials. After installation is successful click finish button. Now it will open a browser with 127.0.0.1/wordpress. Click on the access wordpress link. This will open your website’s front page. To login to your website’s dashboard,type as 127.0.0.1/wordpress/login and then press enter. This will open up wordpress login page. Type the name and password given while installing the software. Press login and this will open up your wordpress dashboard. To get to know more about wordpress tutorials visit our youtube channel. For more tutorials stay tuned with us. You may also like add,delete and upload a theme in wordpress Read the full article
![quartexnet post: XAMPP control user interface does not show up - open - display [Solved] XAMPP control user interface](https://64.media.tumblr.com/b0e9a9e7837e26295d4f3e995c0c23fa/1f817afda2a8447b-ff/s640x960/e2e4bc1ca770e5c18267f8206be7421de0d7e611.png)
XAMPP control user interface does not show up - open - display [Solved] XAMPP control user interface does not show up – open – display [Solved] XAMPP is not showing up when i double click Solution 1: Use Windows to solve the problem This one worked for me. Hover your mouse over the taskbar XAMPP application: Right click and choose Maximize window: You’ll end up with something like this (Fullscreen): Or something like this If so it’s the case, just use the arrows Solution 2: Modify the config file: Close Xampp process. Go and open… View On WordPress
ローカル環境のWordPressサイトをBracketsでライブプレビューする方法(MEMO) PCのローカル環境のWordPressサイトをBracketsでライブプレビューする方法を調べたのでメモします。 ローカル環境はbitnami、MAMPだった場合も手順は変わらないと思います。 bitnami側の準備 （１）bitnamiの「manager-osx」をクリックして起動させます。 （２）「Manage Servers」タブで「Start All」で全て起動させます。 （３）「Go to Application」でWordPressサイトを開きます。 開いたWordPressサイトの http://localhost:8080/wordpress/ のURLをコピーします。 Brackets側の準備 （１）Bracketsで「ファイル→プロジェクト設定」をクリックします。 （２）bitnami側の準備の（3）でコピーしたURLを貼り付けて「完了」をクリックします。 （３）Bracketsでライブプレビュー（Command+Ait+P）をするとWordPressサイトがブラウザで表示されます。 BracketsでWordPressサイトをライブプレビューしながらSCSSでコーディングするとコーディングが捗りそうです。 前にWordPress案件をしてた時にBracketsがあれば倍以上は作業が早かったかもしれません。 その時使っていたDreamweaverはコーディングもライブプレビューも使いにくかったです。（2013年頃） 私のWordPressコーディング技術が初心者なせいもありますけど、ソフトの動作が重いと必然的にコーディング作業も遅くなるとは思います。 環境が構築できたら後はCSSコーディングでデザインカスタマイズかなと思います。 従来通りに「静的サイト制作→PHPコーディング」の手順で行く予定です。 GW期間にAMP対応のブログテーマを作成を目標にしています。 結構、BracketsはWebコーディングに関しては何でもできるエディタのような気はしました。 エクステンション（拡張機能）でかゆいところに手が届く的な感じです。 実際Dreamweaverを使っていた時よりコーディング力は上がっていると感じます。 SASSがスムーズに使えてリアルタイムにコンパイルできる分だけDreamweaverよりはコーディングに集中できるからだと思います。 表示されているサイトは下記のWordPress書籍のサンプルです。 WordPress AMP対応 モダンWeb制作 レッスンブック posted with カエレバ エビスコム ソシム 2017-01-24 Amazon ▼参考になった記事 ローカル環境でWordPressのテーマ(SASS)をBracketsでライブプレビューしながら編集する http://qiita.com/hiro_hosono/items/580352247ebaa450d1aa
About the #Bitnami tag
What is the #Bitnami tag on Tumblr?
#Bitnami is a Tumblr tag people add to their posts so others can find related content. This page collects public posts tagged #Bitnami from blogs across Tumblr so you can browse them in one place.
Can I browse #Bitnami posts without a Tumblr account?
Yes. Zoomblr shows posts tagged #Bitnami with no login or account required — just scroll the feed above. It's completely free.
How do I save an image from a #Bitnami post?
Open the blog of any post you like via its link, then use Zoomblr's post viewer to download the image in full resolution.
